• 0 Posts
  • 593 Comments
Joined 2 years ago
cake
Cake day: May 29th, 2024

help-circle

  • adarza@lemmy.catoLinux@lemmy.mlDoes anyone choose Debian?
    link
    fedilink
    English
    arrow-up
    1
    ·
    14 hours ago

    the same goes for any distribution not just debian. installers and upgrade processes cannot possibly account for the infinite number of unexpected things they could encounter. the more you go ‘off book’ with third-party repositories, backports, manual configuration changes, manual package installs and what-not, the greater the chance for having ‘issues’ with version upgrades.

















  • why I was hitting the memory deadlock on boot, but yours booted OK

    i dunno. was your debian-installer running in lowmem mode? did it add extra stuff because of the detected vm environment (i did notice at least one extra thing here for qemu plus the network drivers needed).

    this trixie-based dietpi here boots at 192mb allocated to the vm, but panics at 160mb.

    the dietpi x64 ‘installer’ iso don’t use the debian-installer. they are clonezilla-based, preconfigured to use an included dietpi image, which does a first-run setup after it’s ‘restored’.



  • tui installer on netinst iso (13.4) says 320mb is required:

    This system does not have enough memory to be supported by this program. At least 320 megabytes of memory are required. If you continue, unpredictable and broken behavior will likely result. You should reboot now and add memory or find some other program to use.

    it does allow you to continue anyway, which switches to ‘low memory’ expert mode install. 320mb also gives this error. 384mb does not, but still enters the special install mode, where i was able to load enough installer components to set up networking to start an install. it did lose part of the display font partway through but it did finish and reboot ok (with ~104mb used). dropped the ram in virt-man to 256mb and it still booted.

    edit: i just installed dietpi on this, which basically shreds debian down to the kernel and not much else, and rebuilds it as dietpi. went on without any issues, not even a complaint with 256mb. htop says 65mb used (this, before adding any server ‘apps’, mind you)… but i might just be able to upgrade a couple dietpi boxes i have that do only have 256mb ram.