Toodarday's questions

I have found a guide that tells me to do the following to get GPU pass through working on 20.04

apt install qemu-kvm libvirt-clients libvirt-daemon-system bridge-utils virt-manager ovmf

lspci -nn returns

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [GeForce RTX 3060 Ti Lite Hash Rate] [10de:2489] (rev a1)
01:00.1 Audio device [0403]: NVIDIA Corporation GA104 High Definition Audio Controller [10de:228b] (rev a1)

/etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=on kvm.ignore_msrs=1 vfio-pci.ids=10de:2489,10de:228b"

Then

update-grub

However when I reboot back I get a plain black screen. Is the process different for 22.04? i9-12900k is the CPU

netstat -an | grep :443 | grep -v TIME_WAIT | wc -l

How do I convert this retunring value of 171 to a variable foo so that If I enter $foo it will return 171.

I am attempting to allow only sFTP connections to a specific folder

/etc/ssh/sshd_config

PermitRootLogin yes
PasswordAuthentication yes
ChallengeResponseAuthentication no
UsePAM yes
PrintMotd no
AcceptEnv LANG LC_*
Subsystem       sftp    /usr/lib/openssh/sftp-server
Match Group demouser
  # Force the connection to use SFTP and chroot to the required directory.
  ForceCommand internal-sftp
  ChrootDirectory /home/demouser/ftp/
  # Disable tunneling, authentication agent, TCP and X11 forwarding.
  PermitTunnel no
  AllowAgentForwarding no
  AllowTcpForwarding no
  X11Forwarding no

I then run the following commands to create the account/folder

groupadd demouser
useradd -g demouser -s /sbin/nologin demouser
chown root:root /home/demouser
chmod 755 /home/demouser/
cd /home/demouser/
mkdir ftp
chown demouser:demouser ftp

The issue I am facing is I am unable to connect when the ChrootDirectory is set to /home/demouser/ftp/ but it works fine when I set it as /home/demouser it doesn't seem to work unless that is a child folder in the designated ChrootDirectory already made.

I have a script that runs to fix any network issues

echo '            routes:' >> /etc/netplan/50-cloud-init.yaml
echo '            - to: 51.89.XXX.XXX/32' >> /etc/netplan/50-cloud-init.yaml
echo '              via: 0.0.0.0' >> /etc/netplan/50-cloud-init.yaml
echo '              scope: link' >> /etc/netplan/50-cloud-init.yaml
echo '            - to: 2XXX:41d0:XX0:XXff:ff:ff:ff:ff' >> /etc/netplan/50-cloud-init.yaml
echo '              scope: link' >> /etc/netplan/50-cloud-init.yaml

However how am I able to prevent it from running twice if those values are already set? I would like to script to check first if each of the lines are present and if they are then it will not add them.

I have the following cronjob setup

@daily /root/trim.sh

/root/trim.sh

fstrim -av

but it just doesn't run. It does when run /root/trim.sh manually. It has chmod +x permissions. What is causing this?

I am currently syncing from two remote servers using:

rsync -a remote1 remote2

The problem I have is remote1 connection is better than remote2 so files seem to be downloading and storing locally causing disk space to fill up and cancel the process.

How could I go about avoiding this problem? (syncing directly from remote 1 > 2 is not an option)

I have recently installed Ubuntu 20.04 onto a USB and noticed I am unable to see it on the "Boot from USB" options. I believe this is due to installing it with the ext4 filesystem. My laptop Aspire 3 a315 doesn't seem to support it.

Question 2: What is expected to be the most common filesystem in 5 years?

So my second question is regarding future proofing. What is expected to be the format that will be most commonly usable for laptops in the next 5 years. Is NTFS a good option? I am not asking in regards to performance I just need it to be usable and what is the most likely format that laptops will still be using.

Right now I am doing the following to allocate an IP address to a specific MAC.

  host 1 {hardware ethernet 02:00:00:ef:0d:20;fixed-address 17x.31.xxx.2xx;option subnet-mask 255.255.255.255;option routers 51.xxx.xx.254;}

How can I modify this so I can use multiple IP address for the MAC 02:00:00:ef:0d:20 ?

Right now I am using the following command to get the output of a videos duration

ffprobe -v error -show_entries format=duration -of default=noprint_wrappers=1:nokey=1 -sexagesimal 'video file.mp4'

The result is 0:33:29.410000

I need this result changed with the following

• An additional 0 must be at the front 0:33:29.410000
• The seconds must be rounded up or down. The final output should be 00:33:29

I am using the current ffmpeg command to convert multiple videos and create a watermark that is a scrolling text that goes from right to left to right every 120 seconds of play time.

find /home/video/ -type f -execdir ffmpeg -i '{}' -filter:v "drawtext=fontfile=/root/FreeSans.ttf:text='QWERTY':[email protected]:fontsize=26:y=h-line_h-30:x=w/20*mod(t\,120),scale=854:480" -pix_fmt yuv420p -c:v libx264 -preset slow -b:v 1000k -minrate 500k -maxrate 2000k -bufsize 2000k -c:a aac -ar 44100 -b:a 128k -movflags +faststart '/home/video/new/{}.mp4' \;

I would like to modify the watermark so it looks something like this

I would like the text shown above to fade in every 120 seconds and last for 15 seconds. Be bold format and the same colour (black).

"qwerty qwerty qwerty qwerty" new line
"qwerty qwerty qwerty qwerty"

Another issue I currently have with the current command I am using is with different video frames. For example if the video is only 800x600 the text will be very large. If the video is 1920x1080 the text will be extremely small. I would like the text size to be adjusted depending on the frame rate. It should look like above in terms of screen size.

I had the same issue as the guy posting on Trouble creating 3TB ext4 partition due to msdos-partition-table-imposed error

The new 6TB drive I got was only issues 2TB by Microsoft so I booted into gparted "Device->Create Partition Table and select "gpt" from the list." I then booted back up into Windows and G: drive was no longer mounted. I deleted disk0 and recreated it inside Windows disk management however as you can see in the screenshot below the disk size is only 5589GB. Should it be more?

I did use about 300GB of data before doing this and I would like to recover that data but both Windows and gparted can't detect anything more than the 5589GB.

I have hundreds of videos in a folder that I want to make a gif for. Each videos length is different but all videos are longer than 30 seconds. I want to take 10 3 second gif images from a video over the course of the video. For example if the video is 25 minutes long a 3 second recorded gif should be taken every 2.5 minutes (150 seconds).

The finished gifs must also have the same name as the video but ending in .gif all videos are .mp4

The gifs should be 560x340

It would be nice to do this with one command to.

I have installed Proxmox on a machine. I need to extend /dev/mapper/pve-data with the unused space of /dev/sdb5

How can I achieve this?

fdisk -l

Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xfbd89a5c

Device     Boot    Start       End   Sectors  Size Id Type
/dev/sda1  *        4096  40962047  40957952 19.5G 83 Linux
/dev/sda2       40962048  43057151   2095104 1023M 82 Linux swap / Solaris
/dev/sda3       43057152 468854783 425797632  203G  f W95 Ext'd (LBA)
/dev/sda5       43059200 468854783 425795584  203G 8e Linux LVM

Disk /dev/sdb: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xafd793e2

Device     Boot    Start       End   Sectors  Size Id Type
/dev/sdb1           4096  40962047  40957952 19.5G fd Linux raid autodetect
/dev/sdb2       40962048  43057151   2095104 1023M 82 Linux swap / Solaris
/dev/sdb3       43057152 468854783 425797632  203G  f W95 Ext'd (LBA)
/dev/sdb5       43059200 468854783 425795584  203G fd Linux raid autodetect

Disk /dev/mapper/pve-data: 199 GiB, 213708177408 bytes, 417398784 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes