#] #] ********************* #] "$d_SysMaint"'Suse/linux Suse specifics.txt' www.BillHowell.ca 04Jan2020 initial To view this file - use a text editor (not word processor) constant width font (eg courrier 10), tab - 3 spaces To unmount a USB drive : $ sudo umount /run/media/bill/Midas/ USBbackup to Suse : see $d_bin""backup.sh", backup_USBdrive_to_ThinkPad To prevent sleep : 15Sep2021 NYET! : Suse menu -> Favourites -> Power management -> Energy saving -> check Screen energy saving, switch off after 30 min Suspend session, after 50 min Button events handling when laptop lid closed : do nothing check even when an external monitor is connected when power button pressed : prompt log out display see also "$d_SysMaint"'Suse/linux Suse specifics.txt' "$d_SysMaint"'Linux/installation of Linux notes.txt' "$d_PROJECTS"'SW install & maintain/Suse install/Suse install notes.txt' "$d_bin"'apps installed.sh' 48************************************************48 24************************24 # Table of Contents : # $ grep "^#]" "$d_SysMaint"'Suse/linux Suse specifics.txt' | sed 's/^#\]/ /' ********************* "$d_SysMaint"'Suse/linux Suse specifics.txt' 25Oct2022 h264 mp4 codec doesn't work 28Sep2022 difficulty finding where to modify default apps ?date? 3 Command Line Tools to Install Local Debian (.DEB) Packages 14Sep2021 USBbackup to Suse (USBbackup recent = Seagate4Tb180404) 24************************24 08********08 #] ??Dec2022 08********08 #] ??Dec2022 08********08 #] ??Dec2022 08********08 #] ??Dec2022 08********08 #] ??Dec2022 08********08 #] 01Dec2022 Bootable USB for Leap 15.4 from https://get.opensuse.org/leap/15.4/?type=desktop#download downloaded updated offline image - 3.9Gb was only 1.5 Gb (maybe compression effect?) YES!!! ark file 2.8 Gb (long time to download!!) 0> 3.9 Gb unpacked software manager download imagewriter didn't use : $ imagewriter -d /dev/sdc '/home/bill/SG6/PROJECTS/SW install & maintain/Suse install/221201 openSuse-LEAP-15.4-CR-DVD-x86_64Build19.2-Media.iso directory/' '/home/bill/SG6/PROJECTS/SW install & maintain/Suse install/221201 openSuse-LEAP-15.4-CR-DVD-x86_64Build19.2-Media.iso directory' +-----+ https://get.opensuse.org/leap/15.4/?type=desktop#download Verify Your Download Before Use Many applications can verify the checksum of a download. To verify your download can be important as it verifies you really have got the ISO file you wanted to download and not some broken version. For each ISO, we offer a checksum file with the corresponding SHA256 sum. For extra security, you can use sha256sum to verify who signed those .sha256 files. It should be 22C0 7BA5 3417 8CD0 2EFE 22AA B88B 2FD4 3DBD C284 For more help verifying your download please read Checksums Help $ sha256sum --check "$d_PROJECTS"'SW install & maintain/Suse install/openSUSE-Leap-15.4-CR-DVD-x86_64-Build19.2-Media.iso' >> gave junk +-----+ sha256sum: boot/x86_64/yast2-trans-it.rpm: No such file or directory boot/x86_64/yast2-trans-it.rpm: FAILED open or read sha256sum: boot/x86_64/yast2-trans-ja.rpm: No such file or directory boot/x86_64/yast2-trans-ja.rpm: FAILED open or read sha256sum: boot/x86_64/yast2-trans-xh.rpm: No such file or directory boot/x86_64/yast2-trans-xh.rpm: FAILED open or read +-----+ >> big screw-up https://www.gnu.org/software/coreutils/sha256sum >> no help $ sha256sum "$d_PROJECTS"'SW install & maintain/Suse install/openSUSE-Leap-15.4-CR-DVD-x86_64-Build19.2-Media.iso' 894b2c10b1b128cc5764d493ab5d4b56b3cab9e0becfeba41355247a675aba28 /home/bill/SG6/PROJECTS/SW install & maintain/Suse install/openSUSE-Leap-15.4-CR-DVD-x86_64-Build19.2-Media.iso >> can't find check each file : $ d_ISO='/home/bill/SG6/PROJECTS/SW install & maintain/Suse install/221201 openSuse-LEAP-15.4-CR-DVD-x86_64Build19.2-Media.iso directory/openSUSE-Leap-15.4-CR-DVD-x86_64-Build19.2-Media/' $ sha256sum --check "$d_ISO"'SUSEgo.png' sha256sum: '/home/bill/SG6/PROJECTS/SW install & maintain/Suse install/221201 openSuse-LEAP-15.4-CR-DVD-x86_64Build19.2-Media.iso directory/openSUSE-Leap-15.4-CR-DVD-x86_64-Build19.2-Media/SUSEgo.png': no properly formatted SHA256 checksum lines found >> nuts, no good $ sha256sum "$d_ISO"'SUSEgo.png' d6aa2d93eeb75d367b1d0388b9d860b535055f2845fc23eea13ce4d5a4499205 /home/bill/SG6/PROJECTS/SW install & maintain/Suse install/221201 openSuse-LEAP-15.4-CR-DVD-x86_64Build19.2-Media.iso directory/openSUSE-Leap-15.4-CR-DVD-x86_64-Build19.2-Media/SUSEgo.png >>> checksum is NOT the same as iso file prior to extraction $ sha256sum "$d_PROJECTS"'SW install & maintain/Suse install/openSUSE-Leap-15.4-CR-DVD-x86_64-Build19.2-Media.iso' >> takes time!! 18:56-18:58 894b2c10b1b128cc5764d493ab5d4b56b3cab9e0becfeba41355247a675aba28 /home/bill/SG6/PROJECTS/SW install & maintain/Suse install/openSUSE-Leap-15.4-CR-DVD-x86_64-Build19.2-Media.iso >> only overall checksum results - same as above!!??!?! Strange, in "$d_ISO" on dirs [boot, docu, EFI, media.1] are checked? $ sha256sum "$d_ISO"'EFI/BOOT/bootx64.efi' be2bb5c4d9148919494a590b582d6b8ca8451e98f2b07f4b1ac65cabd11da325 /home/bill/SG6/PROJECTS/SW install & maintain/Suse install/221201 openSuse-LEAP-15.4-CR-DVD-x86_64Build19.2-Media.iso directory/openSUSE-Leap-15.4-CR-DVD-x86_64-Build19.2-Media/EFI/BOOT/bootx64.efi No good!! : CHECKSUMS has : 2d76666e83fd08f73dd83c4188f884e1c1a9dc7f8879b40763910ed5fcca017a EFI/BOOT/bootx64.efi I give up - just try ISO without SG6 drive? close everything >> looks like ISO image should be OK? 08********08 #] 01Dec2022 user-installed apps list https://forums.opensuse.org/showthread.php/540057-List-All-Applications-Installed-AFTER-Tumbleweed-OS-Install 29-Apr-2020, 00:41#5hcvv's Avatarhcvv hcvv is online now Global Moderator Default Re: List All Applications Installed AFTER Tumbleweed OS Install? Hi, That is something different from what you asked first. And of course I skipped the first paragraph what you said about Windows, because I have no idea what it does or how it works. When you now ask for the software packages installed (of course by root using zypper/YaST) later then the software installed during he istallation of the system, the answer is: make a list and sort it to installation date. Then all later then the system installation date was installed later (you got it). And @malcolmlewis seems to show you a way to look in the logs of zypper/YaST. A sorted list of all installed RPMs (thus not only by zypper/YaST, also done direct using rpm) can also be made by rpm -qa --qf '%{INSTALLTID}:%{NAME}\n' | sort The first field shows the time stamp. It bit difficult readable, but I guess you must be able to work out from the end what you have installed latest. Henk van Velden Howell : rpm -qa --qf '%{INSTALLTID}:%{NAME}\n' | sed 's/\([0-9]\+\:\)//' | sort >"$d_SysMaint"'Linux/installed applications list.txt' >> HUGE!! 2500+ items cat "$d_SysMaint"'Linux/installed applications list.txt' | grep --invert-match "^lib*" | sort >"$d_SysMaint"'Linux/installed applications list no-libs.txt' >> now only 1442 apps Most hyphens are for app series? - try : cat "$d_SysMaint"'Linux/installed applications list no-libs.txt' | sed 's/\([a-zA-Z0-9]\+\-*\)/\1/' | sort -u >"$d_SysMaint"'Linux/installed applications list no-libs-hyphens.txt' 08********08 #] 01Dec2022 Upgrade OpenSuse Leap 15.3 -> 42.1, or Tumbleweed https://en.opensuse.org/SDB:Offline_upgrade recommends offline upgrade : safer & cleaner without residuals KInfoCenter output : Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.76.0 Qt Version: 5.12.7 Kernel Version: 5.3.18-150300.59.93-default OS Type: 64-bit Processors: 4 × Intel® Core™ i7-5500U CPU @ 2.40GHz Memory: 7.5 GiB of RAM OpenSuse Leap 15.4, download image (3.9 Gb) for offline install option-> take checksum +-----+ https://en.opensuse.org/SDB:Offline_upgrade Prepare repository list. If you are going to use your extra repositories, it is easier to change them to point to the new URL. Open a terminal, su - to root, change to directory /etc/zypp/repos.d, make a backup copy of the repo files there into a subdirectory, and edit them, for example running "sed -i 's/15.3/15.4/g' /etc/zypp/repos.d/*.repo" (why not use ${releasever} you will see now). Finally, run "zypper clean" and "zypper ref" — the later will fail if some repo is not found at the new URL. When all the URLs are correct, you can continue. It is easier to do this now, than later during the upgrade with a limited line editor. >> ??repos don't have 15.3... >> no use to all Software Manager downloads But, backup within directory in SG5 : /home/bill/SG6/PROJECTS/SW install & maintain/Suse install/221201 repositories backup sudo cp -rup "/etc/zypp/repos.d/*" "$d_PROJECTS"'SW install & maintain/Suse install/221201 repositories backup/' >> didn't work, just used dolphin file manager +-----+ "$d_SysMaint"'Linux/installation of Linux notes.txt' 28Aug2014 List of user-installed applications http://askubuntu.com/questions/159664/how-to-list-user-installed-applications-not-packages dpkg -l | grep ii >> dpkg is for Debian packages >> find equivalent for OpenSuse +--+ 29-Apr-2020, 06:32 #7 malcolmlewis Default Re: List All Applications Installed AFTER Tumbleweed OS Install? Hi When I hear the word application, I think more of things related to the Desktop Environment used, so perhaps a look at the 'Patterns' installed and perusing the pattern list on the openSUSE Build Service? Fire up YaST Software Management and in the 'View' select 'Pattern', here you can see what packages are installed with that pattern. You could also look at all 'recommended' packages installed as they could be removed, likewise I remove and lock all language packages from being installed... rpm -qa *-lang --qf "%{name}\n" |xargs zypper rm -u zypper al *-lang Last but not least, instead of breaking down, build up via SUSE Studio Express or using kiwi to create your own install as you want it.... 08********08 #] 01Dec2022 Upgrade OpenSuse 1st "$d_bin""backup.sh" - backup drives see below : # 01Dec2022 results : $ bash "$d_bin"'CPU architecture levels for x86-64.sh' # CPU supports x86-64-v2 # CPU supports x86-64-v3 Therefore, proceed with Leap 15.3 -> 15.4 upgrade!!! wait for backup to be completed 08********08 #] 01Dec2022 [AMD, Intel, Red Hat, SUSE] "architecture levels" for x86-64 CPUs. For example x86-64-v2 https://unix.stackexchange.com/questions/631217/how-do-i-check-if-my-cpu-supports-x86-64-v2 For example x86-64-v2 means that a CPU support not only the basic x86-64 instructions set, but also other instructions like SSE4.2, SSSE3 or POPCNT. How can I check which architecture levels are supported by my CPU? edited Jan 28, 2021 at 8:33, Vikki asked Jan 27, 2021 at 8:44m, gioele +-----+ Originally copied from https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/2/diffs With glibc 2.33 or later (Arch Linux, Debian 12, Ubuntu 21.04, Fedora 34, etc.), or patched glibc (RHEL 8), you can see what architecture is supported by your CPU by running: $ /lib/ld-linux-x86-64.so.2 --help Subdirectories of glibc-hwcaps directories, in priority order: x86-64-v4 x86-64-v3 (supported, searched) x86-64-v2 (supported, searched) On Debian derivatives the path is different, you need to run /lib64/ld-linux-x86-64.so.2 --help. edited Nov 16 at 17:59 answered Apr 22, 2021 at 17:22 Uzumaki D. Ichigo +-----+ https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level#architectural_considerations_for_rhel_9 In the summer of 2020, AMD, Intel, Red Hat, and SUSE collaborated to define three x86-64 microarchitecture levels on top of the x86-64 baseline. The three microarchitectures group together CPU features roughly based on hardware release dates: - x86-64-v2 brings support (among other things) for vector instructions up to Streaming SIMD Extensions 4.2 (SSE4.2) and Supplemental Streaming SIMD Extensions 3 (SSSE3), the POPCNT instruction (useful for data analysis and bit-fiddling in some data structures), and CMPXCHG16B (a two-word compare-and-swap instruction useful for concurrent algorithms). - x86-64-v3 adds vector instructions up to AVX2, MOVBE (for big-endian data access), and additional bit-manipulation instructions. - x86-64-v4 includes vector instructions from some of the AVX-512 variants. We've documented the three levels in detail in the x86-64 psABI supplement. The upcoming GCC version 11 and LLVM version 12 releases will support them in -march= arguments. Patches to augment the glibc dynamic loader with a new mechanism (without the power-set construction) have been incorporated into glibc under the glibc-hwcaps moniker. These changes are expected to be part of the upcoming 2.33 release of glibc. +-----+ https://www.phoronix.com/news/openSUSE-Tumbleweed-x86-64-v2 "... The x86-64-v2 requirement limits the Tumbleweek=d CPOU support to roughly Intel CPUs of the past 15 years or on the AMD side hardware withi the past decade. >> Should include my ThinkPad? +-----+ https://unix.stackexchange.com/questions/631217/how-do-i-check-if-my-cpu-supports-x86-64-v2 This is based on gioele’s answer; the whole script might as well be written in AWK: #!/usr/bin/awk -f BEGIN { while (!/flags/) if (getline < "/proc/cpuinfo" != 1) exit 1 if (/lm/&&/cmov/&&/cx8/&&/fpu/&&/fxsr/&&/mmx/&&/syscall/&&/sse2/) level = 1 if (level == 1 && /cx16/&&/lahf/&&/popcnt/&&/sse4_1/&&/sse4_2/&&/ssse3/) level = 2 if (level == 2 && /avx/&&/avx2/&&/bmi1/&&/bmi2/&&/f16c/&&/fma/&&/abm/&&/movbe/&&/xsave/) level = 3 if (level == 3 && /avx512f/&&/avx512bw/&&/avx512cd/&&/avx512dq/&&/avx512vl/) level = 4 if (level > 0) { print "CPU supports x86-64-v" level; exit level + 1 } exit 1 } This also checks for the baseline (“level 1” here), only outputs the highest supported level, and exits with an exit code matching the first unsupported level. edited Jan 27, 2021 at 9:39 answered Jan 27, 2021 at 9:15, Stephen Kitt +--+ On Linux, one can check the CPU capabilities reported by /proc/cpuinfo against the requirements described in the x86-psABI documentation. The following script automates that process (the exit code is the number of the first non-supported architecture level). #!/bin/sh -eu flags=$(cat /proc/cpuinfo | grep flags | head -n 1 | cut -d: -f2) supports_v2='awk "/cx16/&&/lahf/&&/popcnt/&&/sse4_1/&&/sse4_2/&&/ssse3/ {found=1} END {exit !found}"' supports_v3='awk "/avx/&&/avx2/&&/bmi1/&&/bmi2/&&/f16c/&&/fma/&&/abm/&&/movbe/&&/xsave/ {found=1} END {exit !found}"' supports_v4='awk "/avx512f/&&/avx512bw/&&/avx512cd/&&/avx512dq/&&/avx512vl/ {found=1} END {exit !found}"' echo "$flags" | eval $supports_v2 || exit 2 && echo "CPU supports x86-64-v2" echo "$flags" | eval $supports_v3 || exit 3 && echo "CPU supports x86-64-v3" echo "$flags" | eval $supports_v4 || exit 4 && echo "CPU supports x86-64-v4" answered Jan 27, 2021 at 8:44 gioele 08********08 #] 25Oct2022 h264 mp4 codec doesn't work use ffmpeg to convert to ogv!?!? see "$d_SysMaint""video/ffmpeg notes.txt" +-----+ https://linuxiac.com/fedora-and-opensuse-are-dropping-support-for-some-video-codecs/ Fedora and openSUSE Are Dropping Support for Some Video Codecs Oct 5, 2022Fedora and openSUSE are removing H.264, H.265, and VC-1 VA-API video codecs support from Mesa to avoid potential patent issues. Fedora's decision to drop support for several essential video codecs sparked widespread outrage in the Linux community last week. Additionally, openSUSE quickly followed suit, further escalating the situation. The Root of the Problem Here we are talking about software patents and their application to legislation in different countries. In short, some video codecs, such as H.264, are patent-protected by MPEG LA, a US company based in Denver, Colorado. Therefore, their use implies the payment of patent fees. By chance, Red Hat’s lawyers discovered that the codecs used by Fedora via the Mesa library violated patent rules. So naturally, they immediately raised concerns about initiating patent infringement lawsuits against the corporation. What is notable and significant in this case is that these patents only apply to corporations with a presence in the US. In other words, these patent rights do not apply in Europe, where the software patent law differs. As a result, Linux distributions headquartered outside the US or entirely community-driven, with no commercial purpose, are not subject to the risk of infringing on these patent rights. Unfortunately, one of the video codecs targeted for removal from Fedora and openSUSE, H.264, is currently the world’s most used HD video compression standard. First and foremost, it should be stated that this problem will only affect users with AMD-based systems. Why? Because AMD entirely relies on Mesa for these codecs. +-----+ https://forums.opensuse.org/blogs/caf4926/opensuse-13-1-multi-media-restricted-format-installation-guide-149/ >> no longer available +-----+ https://forums.opensuse.org/showthread.php/493132-openSUSE-13-1-MP4(a)-h264-missing-codec 07-Dec-2013, 18:56#2crmrhm crmrhm is online now Parent Penguin Join Date Aug 2008 Location San Francisco Posts 549 Default Re: openSUSE 13.1 MP4(a) h264 missing codec Follow the procedure at https://forums.opensuse.org/blogs/ca...ion-guide-149/ to get VLC and its codecs installed for 13.1 from Packman. https://forums.opensuse.org/blogs/caf4926/opensuse-13-1-multi-media-restricted-format-installation-guide-149/ My installation of this plays mp4 files correctly. Regards, Howard +-----+ https://forums.opensuse.org/showthread.php/536121-How-to-Get-MP4-H-264-Working-on-OpenSuSE-Tumbleweed 08-Jun-2019, 08:49#8malcolmlewis's Avatarmalcolmlewis malcolmlewis jest offline Administrator Join Date Jun 2008 Location East of Podunk Posts 33,555 Blog Entries 15 Default Re: How to Get MP4/H.264 Working on OpenSuSE Tumbleweed Quote Originally Posted by LMH1 View Post But why did ubuntu or openmandriva works better out of the box with that? I guess something is wrong with opensuse here. Hi Looks like a user error Perhaps understanding how OBS and packman works, the packman build service in a lot of cases (especially multimedia) is just an external rebuild service (as in third party) that enables the non-oss features and rebuilds. For example, package X is built and maintained on the openSUSE Build Service and conditions (bcond in OBS speak) are set to disable feature Y, what the packman build service does is create a link to it from the openSUSE build service and then 'enable' feature Y and rebuild. So if you have package X OBS repository active (with feature Y disabled) and packman repository active containing package X (with feature Y enabled) of course you will get conflicts..... The reason is packman resources (both hardware and human) to reduce the package maintenance load where in a lot of cases stuff was copied over changed to enable feature Y and rebuilt, now the bulk of it is automated in it's all maintained in one place, but built on two build instances.... hope that all makes sense? I would suggest just using openSUSE oss, non-oss (if required) and then packman for you multimedia needs. If there are specific packages you are wanting (and multimedia related), ask the third party repository folks to enable a build there? http://packman.links2linux.org/help Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below... Thanks! 08********08 #] 28Sep2022 difficulty finding where to modify default apps eventually, I stumbled on : System settings -> Applications -> default applications -> >> stupid, should have labelled it "Default applications" right in "System settings" page!!! frustrating... +-----+ https://forums.opensuse.org/showthread.php/449768-Open-Suse-11-1-How-to-set-default-browser-MANUALLY 13-Nov-2010, Edward_Iii, joined Jul 2009 Depends on which DE you use. If you use KDE you can change it via SystemSettings->Default-Applications->Web browser. (<-- Not sure about the names of the menus) Then change "mozillafirefox" to "opera" (without quotes). Good luck! >> still very hard to find 08********08 #] ?date? 3 Command Line Tools to Install Local Debian (.DEB) Packages +-----+ https://www.tecmint.com/install-local-deb-packages-in-debian-ubuntu-linux-mint/ 3 Command Line Tools to Install Local Debian (.DEB) Packages Aaron KiliApril 23, 2018 Categories +--+ 1. Install Software Using Dpkg Command Dpkg is a package manager for Debian and its derivatives such as Ubuntu and Linux Mint. It is used to install, build, remove and manage .deb packages. but unlike other Linux package management systems, it cannot automatically download and install packages with their dependencies. To install a local package, use the dpkg command with the -i flag along with package name as shown. $ sudo dpkg -i teamviewer_amd64.deb If you get any dependency errors while installing or after installing and launching a program, you can use the following apt command to resolve and install dependencies using the -f flag, which tells the program to fix broken dependencies. $ sudo apt-get install -f To remove a package use -r option or if you want to remove all its files including configuration files, you can purge it using the --purge option as shown. $ sudo dpkg -r teamviewer [Remove Package] $ sudo dpkg --purge teamviewer [Remove Package with Configuration Files] +--+ 2. Install Software Using Apt Command The apt command is a advanced command-line tool, which offers new software package installation, existing software package upgradation, updating of the package list index, and even upgrading the whole Ubuntu or Linux Mint system. It also offers apt-get and apt-cache command-line tools for managing packages more interactively on Debian and its derivatives such as Ubuntu and Linux Mint systems. Essentially, apt-get or apt do not understand .deb files, they are designed to primarily handle package names (for example teamviewer, apache2, mariadb etc..) and they retrieve and install .deb archives associated with a package name, from a source specified in the /etc/apt/sources.list file. The only trick to installing a local Debian package using apt-get or apt is by specifying a local relative or absolute path (./ if in current dir) to the package, otherwise it will try to retrieve the package from remote sources and the operation will fail. $ sudo apt install ./teamviewer_amd64.deb $ sudo apt-get install ./teamviewer_amd64.deb +--+ 3. Install Software Using Gdebi Command gdebi is a tiny command-line tool for installing local deb packages. It resolves and installs package dependencies on the fly. To install a package, use the following command. $ sudo gdebi teamviewer_13.1.3026_amd64.deb 08***********08 #] 14Sep2021 USBbackup to Suse (USBbackup recent = Seagate4Tb180404) checks : $ diff "$d_bin""start.sh" "/run/media/bill/Seagate4Tb180804/webRawe/bin/start.sh" --suppress-common-lines >> OK $d_bin""backup.sh" : backup_USBdrive_to_ThinkPad() { partition="webRawe" d_src="$d_backupDrive$partition/" d_out="$d_webRawe" backer_rsync partition="PROJECTS" d_src="$d_backupDrive$partition/" d_out="$d_PROJECTS" backer_rsync partition="LMDE2" d_src="$d_backupDrive$partition/" d_out="$d_LMDE" backer_rsync } dir (Gb) ThinkPad USBbackup $d_webRawe 16.2 13.8 $d_PROJECTS 42.6 137.7 is this a problem?? (videos probably) $d_LMDE 16.2 17.2 root ThinkPad directory : 288.1 Gb free of 458.0 Gb so there is sufficient space from $ bash "$d_bin""du_sort.sh" dir='/home/bill/PROJECTS/' du -ch --max-depth=1 "$dir" | sed "s#\(.*\)\t\($dir\)\(.*\)#\3\t\1#" | sort | sed "s#\(.*\)\t\(.*\)#\2\t\1#" # >"$d_temp""du1.txt" see "$d_bin""du_diff.sh" +-----+ 2,5c4,5 < 2021 IJCNN Shenzen, China 12M < 43G < 43G total < 9_My sports & clubs 837M --- > 2021 IJCNN Shenzen, China 93G > 9_My sports & clubs 846M +-----+ 20c19 < Personal & Events 6.8G --- > Personal & Events 9.8G +-----+ >> Ok, I looked at both big dirs, and it's OK The backup seemed to work VERY well! 08***********08 04Mar2020 Problems with "backup computer [to,from] TravelUSB.sh" 1. Permission denied : +-----+ sync --exclude-from="/home/bill/PROJECTS/bin/backup computer [to,from] TravelUSB excludes.txt" "/run/media/bill/SAMSUNG_G4/SWAPPER/Website/Cool stuff/" "/home/bill/SWAPPER/Website/Cool stuff" >"/mnt/ramdisk/backup computer [to,from] TravelUSB log.txt" /home/bill/PROJECTS/bin/standard header.sh: line 26: /mnt/ramdisk/backup computer [to,from] TravelUSB log.txt: Permission denied cat: '/mnt/ramdisk/backup computer [to,from] TravelUSB log.txt': No such file or directory +-----+ >>properly mount ramdisk 2. skipping directory . +-----+ rsync --exclude-from="/home/bill/PROJECTS/bin/backup computer [to,from] TravelUSB excludes.txt" "/run/media/bill/SAMSUNG_G4/PROJECTS/References - stuff/" "/home/bill/PROJECTS/References - stuff" >"/mnt/ramdisk/backup computer [to,from] TravelUSB log.txt" skipping directory . +-----+ >> Oops - caused by moving script code so options undefined... *********** 02Mar2020 update error message I can't get internet (again!!) Update error : Download (curl) error for 'http://packman.inode.at/suse/openSUSE_Leap_15.1/repodata/repomd.xml': Error code: Connection failed Error message: Could not resolve host: packman.inode.at *********** 04Jan2020 search "Suse Linux and how do I unmount a USB drive?" https://unix.stackexchange.com/questions/45820/how-to-umount-a-usb-drive I want to know how to umount my USB drive via command line. I am using Ubuntu 12.04 LTS 32-bit. mount usb-drive edited Aug 19 '12 at 10:15 student asked Aug 19 '12 at 8:05 Pranit Bauva Suppose your usb drive is mounted to /media/usb then it would be sufficient to do sudo umount /media/usb Suppose the your usb is /dev/sdb1 then you could also do sudo umount /dev/sdb1 You may also have a look at the anwers of one of my questions, how to umount all attached usb devices with a single command: https://unix.stackexchange.com/questions/43594/umount-all-attached-usb-disks-with-a-single-command edited Apr 13 '17 at 12:36 Community♦ answered Aug 19 '12 at 8:39 student The command sudo fdisk -l can be helpful if you don't know where a drive is mounted. – Brian Z Mar 13 '15 at 4:12 I tried : $ sudo fdisk -l [sudo] password for root: +-----+ Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk model: Samsung SSD 850 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x7f5a948c Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 960540669 960538622 458G 83 Linux /dev/sda2 960540670 976771071 16230402 7.8G 5 Extended /dev/sda5 960540672 976771071 16230400 7.8G 82 Linux swap / Solaris Disk /dev/sdb: 28.7 GiB, 30752000000 bytes, 60062500 sectors Disk model: Ultra Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x9c3c0ebe Device Boot Start End Sectors Size Id Type /dev/sdb1 32 60062499 60062468 28.7G 83 Linux Disk /dev/sdc: 7.5 GiB, 8004829184 bytes, 15634432 sectors Disk model: USB Flash Drive Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc3072e18 Device Boot Start End Sectors Size Id Type /dev/sdc1 32 15634431 15634400 7.5G 83 Linux Disk /dev/sdd: 60.1 GiB, 64541949952 bytes, 126058496 sectors Disk model: USB Flash Disk Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdd1 63 126058495 126058433 60.1G c W95 FAT32 (LBA) +-----+ >> CRAZY!! This doesn't show the device name!!! would have to use gparted $ sudo umount /run/media/bill/Midas/ >> OK, this worked. I don't know what happens if files are open... # enddoc