iface wlan0 inet manual
    wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf

iface default inet dhcp

The first snippet is for declaring the conf file to be used, and the second is the one wpa_action will use when setting up an access point link. (using ifup wlan0=default)

In that way you can also define additional, different handlings of different setups with different identities.

https://github.com/eylles/devuan-script … cripts/apt

if ya can't see github the devuan scripts has the following mirrors:
https://codeberg.org/eylles/devuan-scripts
https://gitlab.com/eylles/devuan-scripts
https://git.devuan.org/eylles/devuan-scripts

maybe bit "solved" too-early,
it seem the two SSD same/brand/ same denomination/size SA400S3 behave differently;

the earlier tested still show very slow performance with ext4 and "normal" speeds with ntfs.
the other SA400S3 show good write/speed with both ext4 AND ntfs -- on same computer, with same cables, on ssame sata sloet (sata3 speed capable).

so am wondering if the SSD is not somewat bit-defective or some other mystery involved.

The other elephant in the room is firmware behaviour.
Consumer SSDs have a minimum erase-block size and can suffer from free-space fragmentation issues. They usually don't have uniform write performance in general, relying on cache/host memory and a dedicated "fast" area to buffer writes until they can do a more efficient block allocation.

The upshot of all that is that SSDs do quite a lot of sneaky things in the background to appear faster than the flash memory actually is, they need regular "trimming" to release blocks and power-on-idle downtime so the firmware can do garbage collection, wear-leveling, and free-space defragmentation.
If any of that goes sideways (IME usually due to firmware bugs), performance will fall off a proverbial cliff.
Check both drives are running the same firmware revision (and update if any are available), check the wear-leveling counters in SMART, and try a full zero-fill wipe followed by a trim on the problematic drive.

Benchmarks or GTFO.

How strange they're still being manufactured in volume, and the technology (e.g. HAMR) is still under active development.

You were forced to think for yourself. Devuan can run any root filesystem supported by the kernel (as can most distros), the limitation is only in the installer. As for /home... That's utterly trivial to set up after install, with any filesystem you like.

what is PFS

i.e. more paranoia BS, from someone with likely little idea what it actually does or what attacks it might defend against, since they apparently need "step by step" instructions to write a trivial init script.

Next will be out-of-repo "privacy" browsers, VPNs, and whatever go-fast shiny-new-shit is popular on Arch/Artix right now.

"Toxic" OP, complete with entitlement, shouting, and misguided assertions that your personal preference regarding DNS should be a distro-wide default.

I'm not laughing at DoT, I'm laughing at people who consider it not being enabled by default and integrated into some random GUI a "complete showstopper".
Devuan, like Debian, comes with a standard DNS configuration by default. If you want something else, it's on you to read the documentation and set it up.
Likewise init systems - sysv is the default and best supported. If you want something else, all the parts are available but you get to assemble them.

the thing is that when i use "nc" or commander-type for filecopy, the thing copies for nvme-speeds (not in an instant, but in seconds).

i am not sure what is going on there with linux - filemanagers - or my computer as it seems a strange thing for 2026 to occur.

this script :
https://gist.github.com/dnmodder/de2df9 … 0dc66e8db3

instructions:
https://gist.github.com/dnmodder/de2df9 … nt-3582029

source:
https://github.com/paroj/xpad/issues/114

 emacs /usr/local/bin/fix_controller_xbox_360
(paste the code)  and save [ctrl+x , Ctrl+s]

 chmod +x  /usr/local/bin/fix_controller_xbox_360
reconect controller 

root@DELL:~# /usr/local/bin/fix_controller_xbox_360

Works!

add rule  to

/etc/udev/rules.d/71-microsoft-controllers.rules

# nano   71-microsoft-controllers.rules

ACTION=="add", ATTRS{idProduct}=="028e", ATTRS{idVendor}=="045e", DRIVERS=="usb", RUN+="/usr/local/bin/fix_controller_xbox_360"

reconect the controll  and works!

Is it so impossible to create an HDD that can boot on multiple systems like a "live" CD, that no one can even comprehend the question?

I have just set  up HDDs to work like 'live' CDs, with persistence. It's not hard at all. And the inevitable disk crash problems become almost trivial to handle. Full system backup may amount to copy one file.

Has anybody tested exactly how much is won by doing this driver selection and tailoring vs just running a live system with persistence?
A live system with persistence may, generally, be moved around with small problems. And when the compressed 'live' part is < 10 GB, space is not a problem. Slower running might be, but even 15 years ago, that was not a problem for me, with adequate RAM and good disks.
Booting should not be a problem when a small selection of hardware is targeted, and in any case, there seem to be several solutions to that.

thanks for pointing it out,
will test it probably later one since that computer is with devuan 5 if remember correctly, just checked the list, there is gt 730 support, but the (m) is missing.
https://us.download.nvidia.com/XFree86/ … chips.html

but devuan 5 still function perfectly fine for everything that need.

edit: saving this site here foru future reference, maybe can need it sometime
https://linuxcapable.com/install-nvidia … on-debian/

edit2: it seem the driver 418. is from 2019, so probably it will be difficult to install even on devuan 5, so you could always try with devuan 4.0;
have another laptop with an older graphics card nvidia that runs on devuan 3.0 and the newest browser can function just fine (which is what i mostly use on the computer).

https://ibb.co/LhY92wJp

EDIt: it seem there are however other warning present, like "warning - failed to measure (something like 0000 etc)" it does however no longer show up later on the text messages during boot, only at initial screen.