A lot of developers want to go to 3.11 because of the speed improvements, but most distros never have the latest Python version. Using the deadsnakes third party repo is the easiest way aside from compiling it yourself (which is safer and recommended): Step 1 - Add the repo apt-add-repository ppa:deadsnakes/ppa If you get an error about requests then install it:........

In this scenario, let's say you want to clone your OS at the filesystem level and the source system (the system you want to clone from) is in use. Doing a blind rsync / is a big problem because it uses twice as much space for no reason. The reason for this is that with ecryptfs you have a /home/.ecryptfs directory which has the actual encrypted versions of your files and folders. However your home directory (eg. /home/someuser) is mounted. Doing the blind rsync will ca........

apt install software-properties-common add-apt-repository ppa:deadsnakes/ppa apt update apt install python3-pip apt install python3.7 curl gnupg python3.7-dev git ln -s /usr/bin/python3.7 /usr/bin/python3 pip3 install numpy keras_preprocessing curl https://bazel.build/bazel-release.pub.gpg | sudo apt-key add - echo "deb [arch=amd64] http://storage.googleapis.com/bazel-apt stable jdk1.8" | sudo tee /etc/apt/sources.list.d/bazel........

The easiest way is to use SSHand DD or a combination of netcat. SSHwill be a little slower due to encryption but is the most secure way (on two older systems the average clone speed is about 40-50MB/s). This is also OS independent as it doesn't matter what the source OS is because you are literallly cloning the drive so you retain the partition table and settings. Clone HDD using SSH and DD........

user@box:~$ sudo tune2fs -l /dev/md99 [sudo] password for user: tune2fs 1.42.9 (4-Feb-2014) Filesystem volume name: Last mounted on: /mnt/md50 Filesystem UUID: 976a8655-2619-4587-878c-dab07f7b7652 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Fi........

In my case I could login with the initial install but I rsync'd everything over while preserving ownership and permissions to another RAID partition and booted from that.was fine before. The problem is that you are kicked out the second you login and the problem was SELINUX for some reason (perhaps it noticed something strange when it was moved to the new partition) login: pam_unix(login:session): session opened for user root by LOGIN(uid=0) login: ROOT LOG........

Jun 12 10:30:53 kernel: [724514.291670] EXT4-fs error (device md20): ext4_add_entry: bad entry in directory #2552670: rec_len % 4 != 0 - offset=216, inode=2553603, rec_len=94, name_len=84 Jun 12 10:30:53 kernel: [724514.292400] EXT4-fs error (device md20): ext4_add_entry: bad entry in directory #2552670: rec_len % 4 != 0 - offset=216, inode=2553603, rec_len=94, name_len=84 This happened when an unprivileged user was backing up a Windows filesystem, once they ha........

df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_12-lv_root 50G 1.2G 46G 3% / tmpfs 7.8G 0&nb........

I backed up everything in the /mnt/sd_card directory thinking that some dataloss could occur for some reason but purposely left my microSDHC unbacked up thinking that "it won't touch that since it's external" and Samsung's and other manufacturers website even say this (that it won't be affected and not to worry etc). Apparently I was wrong, my microSD was "undetected" and asked to be formatted after the upgrade (there goes 3-months worth of family photos). No........

The best way I could figure out is to use another guest of some sort to do this, while assigning the disk that needs to be resized to the same guest. So say we have /dev/xvda as the guests drive and we've booted it up. We also have /dev/xvdb (this is going to be the image/disk to be resized). In this case it's based on an ext3/4 image. Run e2fsck on it to ensure there are no filesystem errors. e2fsck /dev/xvdb........

This is one in a series of weird things whichIthought was motherboard related (I RMA'd the motherboard), the RAM tests fine with memtest86 and I used badblocks on both RAID 1 members with no errors and smartctl is happy with them. Basically the array crashes the kernel a lot and has issues when writing. [112322.723465] md0: rw=0, want=14958668696, limit=1887460480 [112322.731077] attempt to access beyond end of device [112322.731087] md........

Nov 29 20:17:58 ubuntu kernel: [ 1157.180789] md: md1 stopped. Nov 29 20:17:58 ubuntu kernel: [ 1157.180829] md0: unknown partition table filesystem not responding/reading properly with du or rsync (this needed an fsck). [ 2571.489217] EXT3-fs error (device md2): ext3_lookup: deleted inode referenced: 35923106 [ 2571.942299] EXT3-fs error (device md2): ext3_lookup: deleted inode referenced: 35923110 [ 2571.9568........

I have no idea why but mkfs.ext3 defaults to a patheticlly small blocksize of 1024 bytes/1KB (kilobyte). That means the maximum filesize is ONLY 16GB! With 2KB/2048 bytes you get a 256 GB maximum filesize, and with 4KB/4096 bytes you get 2TB! I finally noticed/paid attention to this after realizing that with rsync and scp that no file larger than 17GB could be transferred. I then realized it must be a file size limit on the partition. Here is what tune2fs tol........

I've tried to find a good sensible solution to cluster with and each technology has it's pros and cons and there is no perfect solution and I've found a lot of "exaggerations" in the applications, benefits and performance of these different filesystems. DRBD I first started off with DRBD and Ihave to say it does live up to the hype, is quite reliable (although it can be annoying to match up the kernel module and user applications since they must match and whe........