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

help-circle
  • adarza@lemmy.catoLinux@lemmy.mlVLC player
    link
    fedilink
    English
    arrow-up
    7
    ·
    14 days ago

    in this case, the platform (i.e. vlc) has literally not changed. it’s essentially the same thing it’s been for going-on twenty years. there has been no updates or upgrades or changes that affect how it looks or runs. version 3.0 is like eight years old. version 2 was pretty much the same, as was version 1 before that. vlc is one of the most stable and consistent software applications on the planet.




  • adarza@lemmy.catoLinux@lemmy.mlDoes anyone choose Debian?
    link
    fedilink
    English
    arrow-up
    1
    ·
    15 days 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.






  • none. 15 year old apu, slow laptop hdd, 2gb ram (some consumed by the graphics). cpu performance of the earliest s939 dual core athlons.

    put a puppy or antix on it, i guess, and hope for the best. with the 8gb max and a small sata ssd it could run something more mainstream.

    update to add: i just reinstalled the latest antix-full over the top of my old one that runs on an old athlon dual core (am2+ 4gb and hdd). creeps a bit over 1gb ram used once you load a page up in firefox. it’ll be ‘usable’, i guess, running one thing at a time and not going crazy with open tabs and windows. still gonna go back on the recycle pile though. i have too many of this era desktop, no takers for them, and not enough room to store 'em.


  • have you actually looked at a snap’s status?

    root@cave:~# lsb_release -d
    Description:    Debian GNU/Linux 13 (trixie)
    root@cave:~# uname -r
    6.12.88+deb13-amd64
    root@cave:~# snap debug sandbox-features|grep confinement
    confinement-options:  classic devmode
    root@cave:~# snap debug confinement
    partial
    root@cave:~# aa-enabled
    Yes
    root@cave:~# snap info --verbose hello-world
    name:    hello-world
    summary: The 'hello-world' of snaps
    health:
      status:  unknown
      message: health has not been set
    publisher: Canonical✓
    contact:   snaps@canonical.com
    links:
      contact:
        - mailto:snaps@canonical.com
    license: unset
    description: |
      This is a simple hello world example.
    commands:
      - hello-world.env
      - hello-world.evil
      - hello-world
      - hello-world.sh
    notes:               
      private:           false
      confinement:       strict
      devmode:           false
      jailmode:          false
      trymode:           false
      enabled:           true
      broken:            false
      ignore-validation: false
    snap-id:      buPKUD3TKqCOgLEjjHx5kSiCpIs5cMuQ
    tracking:     latest/stable
    refresh-date: today at 07:43 CDT
    installed:    6.4 (29) 20.5kB -
    root@cave:~# snap run hello-world.evil
    Hello Evil World!
    This example demonstrates the app confinement
    You should see a permission denied error next
    /snap/hello-world/29/bin/evil: 9: /snap/hello-world/29/bin/evil: cannot create /var/tmp/myevil.txt: Permission denied
    root@cave:~#