Comments

luthis, 1 year ago to lemmyshitpost in Onions are a violation of the terms of service.

Pretty sure it was the onions.

luthis, 1 year ago to linux in Noob question: what to arrange before switching to linux

Note that there isn’t a Linux version of the protondrive app. … I know! what the fuck right?

Secondly, I would just shove Linux Mint onto a USB and use that as a live distro with persistence for a while, just to get used to things. I’m not a fan of debian(/-based) or apt, but it works.

luthis, 1 year ago to linux in Automatic backups of inode tables and partition info for easier data recovery

Oh you’re right it does work… well fuck knows what I was doing wrong before.

Yeah this is a backup in case I like, mv file to /dev/sda1 or something.

Not a backup of the files, but a backup of the structure.

luthis, 1 year ago to linux in Automatic backups of inode tables and partition info for easier data recovery

Ok time to investigate ZFS

luthis, 1 year ago to linux in Automatic backups of inode tables and partition info for easier data recovery

For fun and learning. It’s just another tool to go with file level backup.

And the backup for this is 40mb and really fast, but backing up files even when compressed would be hundreds of GB, maybe terabytes, and then you’re paying for that amount of storage online somewhere, uploading for hours…

luthis, 1 year ago to linux in Automatic backups of inode tables and partition info for easier data recovery

Great tips, thanks!

I’m using ext4 across everything I think.

Can you enable superblocks after you’ve already formatted the drive?

Fdisk saves the offsets so keeping a record of that at least sounds like a good idea.

luthis, 1 year ago (edited 1 year ago) to linux in Automatic backups of inode tables and partition info for easier data recovery

The script takes the drives as arguments:

<span style="color:#323232;">$ pwd
</span><span style="color:#323232;">/usr/lib/systemd/system
</span><span style="color:#323232;">$ cat drive_backup.service 
</span><span style="color:#323232;">[Unit]
</span><span style="color:#323232;">Description=backup fdisk + e2image
</span><span style="color:#323232;">Wants=drive_backup.timer
</span><span style="color:#323232;">
</span><span style="color:#323232;">[Service]
</span><span style="color:#323232;">Type=oneshot
</span><span style="color:#323232;">ExecStart=/usr/bin/backup_meta_data.sh /dev/sdc1 /dev/sdb1
</span><span style="color:#323232;">
</span><span style="color:#323232;">[Install]
</span><span style="color:#323232;">WantedBy=multi-user.target
</span>

Set to run at 3:40am every day, but probably could be once weekly really.

<span style="color:#323232;">$ cat drive_backup.timer 
</span><span style="color:#323232;">[Unit]
</span><span style="color:#323232;">Description=timer to run drive backup
</span><span style="color:#323232;">Requires=drive_backup.service
</span><span style="color:#323232;">
</span><span style="color:#323232;">[Timer]
</span><span style="color:#323232;">Unit=drive_backup.service
</span><span style="color:#323232;">OnCalendar=*-*-* 03:40:00
</span><span style="color:#323232;">
</span><span style="color:#323232;">[Install]
</span><span style="color:#323232;">WantedBy=timers.target
</span>

Should be fairly self-explanatory.

<span style="color:#323232;">$ cat /usr/bin/backup_meta_data.sh
</span><span style="color:#323232;">#!/bin/bash
</span><span style="color:#323232;">
</span><span style="color:#323232;">working_dir=/home/st/drive_recovery/working
</span><span style="color:#323232;">backup_dir=/home/st/drive_recovery
</span><span style="color:#323232;">backup_date=$(date +%Y%m%d-%H%M)
</span><span style="color:#323232;">
</span><span style="color:#323232;">mkdir -p $working_dir
</span><span style="color:#323232;">
</span><span style="color:#323232;">sudo fdisk -x > $working_dir/$backup_date.fdisk
</span><span style="color:#323232;">
</span><span style="color:#323232;">for var in "$@"
</span><span style="color:#323232;">do
</span><span style="color:#323232;">	clean=$(echo $var | sed 's;/;-;g')
</span><span style="color:#323232;">	sudo e2image $var $working_dir/$backup_date.$clean
</span><span style="color:#323232;">done
</span><span style="color:#323232;">
</span><span style="color:#323232;">sudo 7z a $backup_dir/$backup_date.archive $working_dir/"$backup_date"*
</span><span style="color:#323232;">sudo rm $working_dir/"$backup_date"*
</span>

luthis, 1 year ago to linux in FOUND file in device by hex content using wxHexEditor

Yeah definitely share your config! I’ve only just scratched the surface with wxHexEditor

luthis, 1 year ago to linux in FOUND file in device by hex content using wxHexEditor

Thanks! I will keep it up!

luthis, 1 year ago to linux in How to take actions on multiple docker containers at once

I needed a way to pass an argument into the command so it can be used in name=“$1”

luthis, 1 year ago to linux in How to take actions on multiple docker containers at once

Dude, I use the CLI all day, every day and I can’t freakin remember half the commands I need.

If it’s something I use often, I’ll make an alias even if it’s just so I can run ‘alias’ in the terminal to get a list of things I use often.

luthis, 1 year ago to linux in How to take actions on multiple docker containers at once

If I eventually get around to using a GUI, I’ll check out portainer

luthis, 1 year ago to linux in How to take actions on multiple docker containers at once

<span style="color:#323232;">Usage:  docker stop [OPTIONS] CONTAINER [CONTAINER...]
</span><span style="color:#323232;">
</span><span style="color:#323232;">Options:
</span><span style="color:#323232;">  -s, --signal string   Signal to send to the container
</span><span style="color:#323232;">  -t, --time int        Seconds to wait before killing the container
</span>

Unfortunately no filter here

luthis, 1 year ago to linux in How to see enabled services that have been stopped [systemd]

I think you’re thinking of

systemctl list-units --type=service --state=stopped

status gives the state of the system and a cgroup tree

luthis, 1 year ago to linux in How to take actions on multiple docker containers at once

Is there a way to do this without cd-ing to the directory with the compose file first?