March 2023 - openSUSE Users - openSUSE Mailing Lists

Finding recent work directories
by Robert Webb 04 Mar '23

04 Mar '23

Since I often get side-tracked and forget what I was doing, I wrote a script to find directories with recent (or otherwise selected) files in them. That makes a better list than sorting directories by their own modification times. This script, 'finddirs_by_latest_file', allows to restrict the search with extra find expression terms, but I usually just run the second script below, 'fblf100', which invokes finddirs_by_latest_file to make two lists; for the latest 5 and 100 days (or whatever time periods given). Excuse all the script boilerplate. Carlos, this may help you find your router config info. --<cut>------------------------------------------------------------------ #!/bin/sh # finddirs_by_latest_file.sh 2022-06-30 rw # # Outputs a list of directories of found files, sorted by the time of # their most recently modified file, and prefixed by a file count. #-----<lib/s/template-errx-getopts.sh>----------------------------------- CMD=finddirs_by_latest_file VERSION=0.1 export LC_COLLATE='C' Cmd=`basename "$0"` umsg() { #------<USAGE>--------------------------------------------------------- printf 'usage: %s %s\n' \ "$Cmd" '[--sdir] [find_options] <find_starting_point>... [find_expression]' \ '' '' \ 'The' 'find_expression, if any, is prepended to an implied:' \ ' -type f' '-exec...' } errmsg() { # usage: errmsg [msg_line ...] test 1 -le "$#" || return 0 printf "${Cmd}: %s\\n" "$@" >&2 } usage() { # for output to stderr, and error exit: usage [msg_line ...] # for normal exit: usage help if [ x"$*" = x'help' ] ;then umsg ;exit else errmsg "$@" ;umsg >&2 ;exit 2 fi } errx() { # usage: errx <exitcode> [msg_line ...] if expr x"${1-}" : x'[1-9][0-9]*$' > /dev/null ;then ExCode="$1" ;shift else ExCode=3 ;set -- "$@" "$BUG: errx(): missing exit code" fi errmsg "$@" ;exit "$ExCode" } BUG="error: software bug" errxbug() { errx 3 "$BUG: $@" } exists() { # usage: exists <path> test -e "${1:?'exists(): null or missing arg'}" || test -h "$1" # test -f "${1:?'exists(): null or missing arg'}" || test -d "$1" \ # || test -h "$1" || test -b "$1" || test -c "$1" || test -p "$1" } #------------------------------------------------------------------------ # Option defaults SORT_BY_DIR_f=false #XXX HACK: '--sdir' option is only recognized when it is first if [ x"${1-}" = x'--sdir' ] ;then SORT_BY_DIR_f=true shift fi GOPTSTRING='hV' while getopts ":$GOPTSTRING" OPT ;do case "$OPT" in #----- h) usage help ;; V) printf 'RW %s %s\n' "$CMD" "$VERSION" ;exit ;; :) usage "missing argument for option: ${OPTARG}" ;; \?) usage "invalid option: ${OPTARG}" ;; *) errxbug "getopts optstring: option: ${OPT}" ;; esac done shift `expr $OPTIND - 1` if [ x"$SORT_BY_DIR_f" = x'true' ] ;then sort_by() { sort -k 3 -k 2,2n ;} else # sort by time, then by dir (default) sort_by() { sort -k 2,2n -k 3 ;} fi #------------------------------------------------------------------------ W=' *[^ ][^ ]* ' # find files: stat <seconds_since_Epoch> <path> # sed: truncate last path component (to parent dir), use '.' if empty, # or '/' if at root # sort by dir, then by recent to old # uniq: most recent of each dir. prefix with file count # sort by time, then by dir (unless '--sdir' option: sort by dir) # sed: remove seconds field export TMPDIR=~/tmp TEMPF=`mktemp --tmpdir "$CMD.XXXXXXXXXX.temp"` \ && trap 'rm -f -- "$TEMPF"' EXIT \ || exit find -H "$@" -type f -exec stat -c '%Y %n' {} + > "$TEMPF" || exit sed -e ' s+^$'"$W"'$[^/]*$+\1.+ t s+^$'"$W"'/$[^/]*$+\1+ t s+^$'"$W"'.*$/[^/]*$+\1+ ' "$TEMPF" \ |sort -k 2 -k 1,1nr \ |uniq -c -f 1 \ |sort_by \ |sed -e 's+'"$W"'+ +2' --<cut>------------------------------------------------------------------ --<cut>------------------------------------------------------------------ #!/bin/sh # fblf100 2021-12-07 rw TOP=~ usage() { printf 'usage: fblf100 [#_by_time_days [#_by_path_days]]' >&2 exit 2 } { printf '=== %s days, in order\n' "${1:-5}" finddirs_by_latest_file "$TOP" -mtime -"${1:-5}" \ || usage printf '\n=== %s days, sorted\n' "${2:-100}" finddirs_by_latest_file --sdir "$TOP" -mtime -"${2:-100}" \ || usage } \ |less --<cut>------------------------------------------------------------------ -- Robert Webb

6 9

So much for all the "Secure Boot" hype...
by David C. Rankin 03 Mar '23

03 Mar '23

Interesting thread: https://www.theregister.com/2023/03/01/blacklotus_malware_eset/ While that article regard windows, the same would likely apply to the unified kernel image if the system is hijacked before it loads. -- David C. Rankin, J.D.,P.E.

2 1

Enlarging BTFS filesystem on Tumbleweed.
by Frank McCormick 03 Mar '23

03 Mar '23

I want to enlarge the file system on my Tumbleweed partition and even after Googling the situation, I feel the whole procedure is definitely above my pay grade :) I have a 500 gig main drive split into various partitions. Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors Disk model: KINGSTON SA400S3 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: 0xf73048ad Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 489330687 489328640 233.3G 83 Linux /dev/sda3 489334782 937699691 448364910 213.8G 5 Extended /dev/sda5 489334784 712566783 223232000 106.4G 83 Linux /dev/sda6 712568832 933502975 220934144 105.3G 83 Linux /dev/sda7 933505024 937699691 4194668 2G 82 Linux swap / Solaris Tumbleweed is on sda6, Debian Sid on sda1 using ext4, Fedora is on sda5 also with ext4 with swap space on sda7. I would like to delete Fedora from sda5 and enlarge sda6 to include that space . I'm planning KVM in Tumbleweed with a version of Fedora. What is the best way to go about this? I know partition work can only be done with the disk not mounted so it appears I'd have to boot from an external utility. If possible I'd like suggestions on the best way to proceed. From what I've read a BTRFS file system can only be enlarged from the front and not from the rear? All help appreciated. Thanks

3 3

Video Borked Again
by Mark Misulich 03 Mar '23

03 Mar '23

Hi, I am running Tumbleweed with KDE plasma version 5.27.1, KDE Frameworks version 5.103.0, QT version 5.15.8, kernel version 6.2.0-1-default (64 bit), Graphics Platform X11. My graphics controller is: VGA compatible controller [0300]: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (pro g-if 00 [VGA controller]) I previously had problems with video and reported in January on the list that I had an old graphics card and ran nouveau as the video driver. Since then I upgraded the graphics card to an Nvidia GT 1030 and now use nvidia G05 as the video driver. I did a zypper dup on two computers I tend, that both run Tumbleweed. In the update kernel 6.2.0-1 was installed, and afterwards neither computer will boot to graphics display. I found that I could still boot to normal graphic display with the previous kernel 6.1.12-1.1. I also found that I can still boot up to graphic display with the 6.2.0-1 kernel in recovery mode. But I don't think the computer is using the Nvidia drivers in recovery mode, the screen doesn't look the same. I've tried to reinstall all the nvidia kernel drivers, but it hasn't changed anything and allowed the 6.2.0-1 kernel to boot normally to graphics display. Here's a link to a paste of the /.local/share/xorg/Xorg.0.log https://paste.opensuse.org/pastes/9ba3a24b019c Hopefully it is a start for the list to figure out what happened in order to advise me how to fix this. Regards, Mark

4 3

[oS-en] What means this error? (systemd)
by Carlos E. R. 02 Mar '23

02 Mar '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Lately I'm seeing a lot of these: <3.6> 2023-03-01T22:56:13.184610+01:00 Telcontar systemd 1 - - Reloading. <3.3> 2023-03-01T22:56:13.490948+01:00 Telcontar systemd 5495 - - /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1. <3.5> 2023-03-01T22:56:13.547410+01:00 Telcontar systemd 1 - - /usr/lib/systemd/system/rpc-statd.service:14: PIDFile= references a path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file accordingly. <3.6> 2023-03-01T22:57:03.897124+01:00 Telcontar systemd 1 - - Reloading. <3.3> 2023-03-01T22:57:04.182654+01:00 Telcontar systemd 5579 - - /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1. <3.5> 2023-03-01T22:57:04.239124+01:00 Telcontar systemd 1 - - /usr/lib/systemd/system/rpc-statd.service:14: PIDFile= references a path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file accordingly. <3.6> 2023-03-01T22:57:44.853856+01:00 Telcontar systemd 1 - - Reloading. <3.3> 2023-03-01T22:57:45.151554+01:00 Telcontar systemd 5626 - - /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1. <3.5> 2023-03-01T22:57:45.215647+01:00 Telcontar systemd 1 - - /usr/lib/systemd/system/rpc-statd.service:14: PIDFile= references a path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file accordingly. <3.6> 2023-03-01T22:58:29.288683+01:00 Telcontar systemd 1 - - Reloading. <3.3> 2023-03-01T22:58:29.552762+01:00 Telcontar systemd 5682 - - /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1. <3.5> 2023-03-01T22:58:29.610571+01:00 Telcontar systemd 1 - - /usr/lib/systemd/system/rpc-statd.service:14: PIDFile= references a path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file accordingly. <3.6> 2023-03-01T22:58:35.053561+01:00 Telcontar systemd 1 - - Reloading. <3.3> 2023-03-01T22:58:35.345362+01:00 Telcontar systemd 5712 - - /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1. <3.5> 2023-03-01T22:58:35.407234+01:00 Telcontar systemd 1 - - /usr/lib/systemd/system/rpc-statd.service:14: PIDFile= references a path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file accordingly. That file is: [Unit] Description=NFS status monitor for NFSv2/3 locking. DefaultDependencies=no Conflicts=umount.target Requires=nss-lookup.target rpcbind.socket Wants=rpc-statd-notify.service After=network.target nss-lookup.target rpcbind.socket PartOf=nfs-utils.service [Service] Environment=RPC_STATD_NO_NOTIFY=1 Type=forking PIDFile=/var/run/rpc.statd.pid <========= ExecStart=/usr/sbin/rpc.statd What is wrong? Can I do something about it? - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY//Lwhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVi0AAoIsCQX+pfmFaleXyh2zG CIS5vT/4AJ0R2pLEDnTo8TiS8eFQRPsStMshqQ== =Dug+ -----END PGP SIGNATURE-----

4 12

[oS-en] Obtaining external IP
by Carlos E. R. 02 Mar '23

02 Mar '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I use "checkip.dyndns.org" to obtain my router external IP in scripts. I don't have yet IPv6, but my question is, can someone that does have IPv6 test it and find out if it writes the IPv6 address? And if not, is there an alternative query site to find that one, suitable for scripts? Thank you. - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY/38TRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVa4kAnjweCuxlWfZDdORk9Bl4 F7XpudX9AJ9SGHWhJiSffQlE/lGlAoYk/E7K4w== =KzjU -----END PGP SIGNATURE-----

5 26

A little bit weird - /etc/resolv.conf is not being populated
by Per Jessen 01 Mar '23

01 Mar '23

>From the mythv thread - I have just repeated this issue, on Leap 15.1. (I know its EOL, but I don't have a choice). a) after rebuilding the initrd, the first boot - just the standard template in /etc/resolv.conf, no nameserver. firewalld is running. b) 2nd reboot, no changes. Still an empty /etc/resolv.conf. The wicked lease information is from last night. c) stopped and disabled firewalld, 3rd reboot. Now the lease info was updated and so was /etc/resolv.conf. Weird stuff. d) enabled firewalld and rebooted. Empty /etc/resolv.conf. I would try this out on 15.4 and 15.5, but NFS installations don't work. I guess I could do a zypper dup. Anyone have any suggestion as to how or why firewalld might interfere with the populating of /etc/resolv.conf ?? Surely that's crazy. -- Per Jessen, Zürich (1.5°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

7 23