You are not logged in.
Pages: 1
That looks advanced (good) but I'm slightly bewildered why you'd backup /dev, /proc, /sys, /run, /tmp, swap when these are unique to not only each computer but sometimes current user/session, and the first three get recreated on reboot, and others (other than if you build packages saved to /tmp) don't matter after reboot. Anyway, I want to develop my own script(s) like this. If I do it, I'd backup what I described (before rsync) because those seem more important.
My family has three Devuan PCs and will get a fourth rebuilt. I also have four Debian virtual private servers (VPS) which unfortunately run in something such as OpenVZ with systemd so didn't work to convert to SysVInit and still be able to reboot properly (did work for daemons while they were up)... bot those VPS are mostly off-topic; just saying I use Debian for some serious uses since maybe 1999 when it was still how Devuan is now, such as for workstations for computer programming/science (CS) and servers.
I have a set of configuration files I use for family PCs such as /etc/pam.d/common-auth, /etc/sudoers, /etc/default stuff, /etc/passwd, /etc/group, some /etc/apt*, /etc/inittab, /etc/inetd.conf, /etc/nanorc, /etc/screenrc, /etc/hosts template, /etc/resolv.conf, /etc/dhcp/dhclient-enter-hooks.d, /etc/aliases, /etc/rc.local* & /etc/profile.d files (my own environment.sh, functions.sh though were for bash), /var/spool/cron/crontabs, /usr/local/{bin|lib}, /etc/X11, etc. I was pretty disappointed our 101-key IBM model M keyboards were undetected: you assumed 104-key/Windows so I needed /etc/default/keyboard, but I also have /etc/default/grub for improvements including reasonable/non-hurried boot time.
Are there any other configuration files you'd suggest? I know some are in /var, which leads to something else.
I've been trying to use AMD's OpenCL on these PCs. Often amdgpu-install works once on a PC but if the driver doesn't work so you have to uninstall & reinstall older, it no longer installs or sometimes might then doesn't work--network problem? Might take some tens minutes or hours or just another day/week until any version installs again. What I found is rsyncing /*bin, /etc (after backup like fstab, files containing hostname), /lib*, /opt, /srv, /usr, /var from another Devuan workstation/server fixes this and immediately makes OpenCL installed and working. Is there a 'right' way to do this, like I know some configuration is also in /var or maybe some machine-specific files are installed elsewhere? It'd also be a way one might quickly copy a Devuan install from an old to new PC without having to do an entire new installation.
Two the workstations--now more servers--I do this with are identical hardware except slightly different multi-function hubs (media dashboards for memory card readers, USB, audio, eSATA, molex power, etc.) though I was careful to not rsync /boot (despite they don't boot UEFI) or various specific/system stuff (/dev, /proc, /run, /sys, /tmp). I'd guess anything different these two have is in /lib/modules and part of the main kernel packages anyway: I didn't install any additional firmware (well, likely main package, but didn't choose individual firmware packages) just some might get loaded (happens somewhere else?) in each but not the other.
Suppose those two are exactly the same, or if two have slightly different CPU, system-/logic-/main-/mother-board or peripherals, if you have preset/template configuration but want to save time by rsyncing, what's the right way to do this: stuff to omit or add or edit or look out for? In /etc I just did 'grep -ir hostname *' for the hostname and it was quick, easy to fix, but configuration elsewhere (/var?) is another matter (might take hours to grep)... if you try this, however make sure to backup /etc/fstab and all /etc/* containing hostname and restore before any rebooting. If you don't, the reboot process will halt, and you have to remount '/' rw and restore fstab, and you may have hostname/network issues. No big deal but on one of several occasions I made this mistake, which if someone is new to this process might feel a bit intimidating (for an old UNIX user it was all kind of obvious).
When the installation CD/DVD is relatively small but we download some GB other packages, and instead of editing all configuration by hand on each new installation, I prefer presets/template for those, and in the case of something such as OpenCL no longer completing installation, then I find cloning with rsync to be easiest instead of trying for days and not being able to number-crunch for Berkeley Open Infrastructure for Network Computing (BOINC) for science until later.
I hope I didn't scare uther, chris2be8 away by originally not saying as much, but I'll elaborate. I use OpenCL for number-crunching, such as Berkeley Open Infrastructure for Network Computing (BOINC) and sometimes cryptocurrency mining. It varies. I crunched more for BOINC than 96% of crunchers (since I had a 19.2 GFlops workstation when many weren't even 1/8 that) and still like doing so much. I don't know how BOINC uses; all I know is I need OpenCL: don't know I can get away with parts. I usually install like the following.
amdgpu-install --usecase=opencl --opencl=rocr --no-32 --no-dkms --accept-eula
Last night I did get a RX 5700 XT working by rsyncing most a workstation/server to another then restoring original fstab, etc... I'll ask about this in another thread.
I wrote what I mostly use, but when my *BSD & Slackware workstation broke down, I had to use family Devuan one while, and it was much better than using regular Debian, Kubuntu/Neon, Xubuntu/Mint, RedHat, and easier than both Gentoo and Arch/Artix. Now I'm asking about OpenCL on Devuan 4 which I consider the best OS for my family's PCs. What I use mostly doesn't get automatic updates or otherwise would be too hard for them to add stuff, but Devuan at least can use KDE's software installer, though we all now use XFCE with KDE programs for a few years. I guess in a few weeks/months I'll upgrade them to Devuan 5 (I probably had been using development/experimental/testing version if I hadn't just made a typographical error).
I was able to use AMD's ROCm/OpenCL on Devuan 4 with Radeon RX 6900 XT, but not RX 5700 XT, nor RX Vega 64, so I want to set this thread unsolved. Sometimes a newer driver doesn't work but older one does, and in the process of installing & uninstalling several, often the installer runs but doesn't even install anything... sometimes it does; sometimes it doesn't.
I see amdgpu-install script now lists Debian inside so tried adding Devuan.
I just want to install OpenCL, not Docker.
OpenCL works for all AMD display/video/graphics cards (which means desktop or server) not too old... in this case, Radeon RX Vega64 & 5700 & 6900 & in future 7900 XT(X)s... CPU & system-/logic-/main-/mother-board is irrelevant (maybe unless not too old, but they're i7s new enough): OpenCL is only for these graphics cards.
You didn't even specify what exactly you need ROCm for [...]
OpenCL
As a mainly Slackware GNU/Linux user, for which standard method (if you want support) is install entire OS (and for which OpenCL for AMD is combined as one extra package) I don't bother with what type of OpenCL programs (BOINC.Berkeley.edu , miners) may use; I plan to just install entire OpenCL. I don't like installing bits & pieces until a non-development OS says you need a 'dev' package (not separated out in development OS) or something fails then you need to find dependencies of dependencies of dependencies to 100th level; I plan to just install entire OpenCL.
I'm just left with more questions than I started with: after a few years, why isn't there the rocm-all package yet, and otherwise, what's the full list what I need or how/where do I get that?
On Devuan 5 (or when stable, newer) can one install OpenCL/AMDGPU-PRO, and how? ROCm didn't work for me in the past, but might be AMDGPU-PRO's basis now, which lately works fine, and one can install only its OpenCL part... or is there a better way? All I found on this topic was old/outdated material for older Devuan and much older Debian.
Pages: 1