Conversation

Notices

1. I love-hate resistances (envelopeme@annihilation.social)'s status on Tuesday, 06-Feb-2024 18:15:01 JST I love-hate resistances
   i dropped the plan to run slack on that pi. reasons being:
   1. the rpi 3b+ isn't supported by the project. i'm worried to be left alone with important fixed. it works
   2. i couldn't find a bare installer for the non-current release 15 for the pi. there are no directories for it. i know it could be done nevertheless, takes more effort
   3. release 15 is compiled for armv7. i guess that also means it's 32-bit only
   4. i don't want to hammer the sd with daily updates from current
   5. the pi will be directly facing the wrath of the big bad internet. hence i can't compromise on security (because of current) and stability (also because of it)
   • † top dog :pedomustdie: (dcc@annihilation.social)'s status on Tuesday, 06-Feb-2024 18:15:00 JST † top dog :pedomustdie:

     in reply to
     @envelopeme If you want to do it the better way https://docs.slackware.com/slackwarearm:inst_sa64_cur (at the bottom) for 32bit you can only do stable last i checked.
   • † top dog :pedomustdie: (dcc@annihilation.social)'s status on Tuesday, 06-Feb-2024 18:29:05 JST † top dog :pedomustdie:

     in reply to
     @envelopeme The hardware is just arm, unless arm board suddenly get fucked you have nothing to worry about.
   • I love-hate resistances (envelopeme@annihilation.social)'s status on Tuesday, 06-Feb-2024 18:29:06 JST I love-hate resistances

     in reply to

     • † top dog :pedomustdie:
     @dcc 32-bit should be fine for performing the basic tasks of a router. i know it's doable but it'll take a lot of effort. i haven't realmed into this kind of installation before
     i'm more worried about the lack of support for the pi3, specially given it will be facing the public internet