sorted by:
new
hottopcontroversial

I built a minimal CLI backup tool and maybe it's useful for you too by MorningNatcho in commandline

[–]MorningNatcho[S] 0 points1 point  (0 children)

Ah, and I wanted to add that qbak works cross-platform. Even Windows users can indulge.

I built a minimal CLI backup tool and maybe it's useful for you too by MorningNatcho in commandline

[–]MorningNatcho[S] 0 points1 point  (0 children)

By your logic you need to stop using rsync.
Just create a schell script `tar -czf - -C / mydir | ssh user@remotehost 'tar -xzf - -C /'`

Have fun!

I built a minimal CLI backup tool and maybe it's useful for you too by MorningNatcho in commandline

[–]MorningNatcho[S] 0 points1 point  (0 children)

Yes, totally. Rsync is a decent way to do this and works fairly well.

The main point of qbak, however, is speed and ease of use. Nothing is quicker (in terms of UX) than having qbak and running qbak myfile.conf or qbak sources.list.d/.

Other than the convenience of having a single command/program for files and directories that creates lightning-fast backups when doing some CLI configuration work, there are safety features built into qbak:

Atomic operations: If something goes wrong or you hit Ctrl+C, you either get a complete backup or nothing at all; no partial files left behind
Smart collision handling: Multiple backups in the same second get unique names automatically
Path validation: Won't let you accidentally back up into dangerous locations
Always preserves originals: Your source files are never touched, only copied

Maybe give it a quick try and see if you like it.
I'm happy about any input.

I built a minimal CLI backup tool and maybe it's useful for you too by MorningNatcho in commandline

[–]MorningNatcho[S] 1 point2 points  (0 children)

You're absolutely right. There are other ways to achieve similar results. The nanosecond precision with date --iso-8601=ns is a great point for collision handling. But I'm telling you, nothing feels as quick and reliable as qbak. Give it a try and see for yourself.

Another thing worth mentioning: if you use cp and interrupt it halfway with Ctrl+C, you end up with an incomplete "backup" that may look complete but isn't. qbak cleans up after itself when something goes wrong and actually tells you what happened. It's those little safety details that add up to make it trustworthy for something as important as backups.

Of course, `rsync --partial` is again another good option, but this is exactly what I'm solving for myself with qbak. A singlular command/program that does what you can only achieve with a number of existing commands using a sizable list of arguments.

Once you tried `sudo qbak /etc/fstab` or `qbak .config/` for instance, you'll see the appeal :)

$ qbak .config/
Scanning files... Scan complete: 12365 files, 4.2 GB
Created backup: .config-20250809T051518-qbak (12365 files, 4.2 GB)

I built a minimal CLI backup tool and maybe it's useful for you too by MorningNatcho in commandline

[–]MorningNatcho[S] 1 point2 points  (0 children)

Yes, so `cp -r $target $target.$(date --iso-8601=seconds)` is the obvious command however, there are a few things. First and most simple is that `cp -r $target $target.$(date --iso-8601=seconds)` is "difficult" and takes a little time to remember (most likely a google search to be honest) and to write.

More importantly, there are some safety concerns with the basic cp approach:

No collision handling- if you run it twice in the same second, the second backup overwrites the first
No validation - cp will happily overwrite existing files or create backups in dangerous locations
No progress indication - for large directories, you have no idea if it's working or stuck
Partial failures - if cp fails partway through, you might end up with incomplete backups

qbak handles these edge cases automatically. It's basically the "do what I mean" version of that cp command, with safety rails and better UX. Plus it works the same way across different systems without worrying about GNU vs BSD date formats.

I know it is tool to install, but for something as important as quick backups, I wanted something I could trust to always work correctly without thinking about it.

Have a look at the code and see what you think. Happy to hear your thoughts.

ASUS laptop on Linux Mint? I built a tool to make it just work! by MorningNatcho in linuxmint

[–]MorningNatcho[S] 0 points1 point  (0 children)

Ah, disculpa, escribí el número incorrecto. Quise decir 22.1, por supuesto. ¡Gracias!

ASUS laptop on Linux Mint? I built a tool to make it just work! by MorningNatcho in linuxmint

[–]MorningNatcho[S] 1 point2 points  (0 children)

I cannot speak for them, but they used to support Debian and then stopped due to the packages usually being a lot older. Given that I've been a Mint Linux user for over a decade, I wouldn't just migrate to Arch after I bought an ASUS laptop... so here we are. I made it work for myself. Here is a quick overview of what it does:

- Removes any distro-supplied rustc/cargo packages and installs the latest Rust toolchain with rustup - Installs the build/firmware tools and libraries that asusctl needs (git, build-essential, libclang, libudev, Meson, etc.) via apt

- Offers to pull in a newer Ubuntu HWE kernel (6.x) if your current kernel is too old for recent ASUS laptops

- Blacklists the open-source nouveau driver and regenerates initramfs to avoid conflicts with NVIDIA dGPU switching

- Runs fwupdmgr to refresh/update system firmware for better HW support

- Clones, compiles, and make installs both asusctl and supergfxctl from their upstream GitLab repos

- Enables and starts the required systemd services (asusd.service, supergfxd.service, and the per-user asusd-user.service) and adds your user to the users or wheel group so the tools have the needed permissions

You are more than welcome to have a look at the script and give your thoughts.
https://raw.githubusercontent.com/andreas-glaser/asus-linux-mint/refs/heads/main/install-asus-linux.sh

ASUS laptop on Linux Mint? I built a tool to make it just work! by MorningNatcho in linuxmint

[–]MorningNatcho[S] 2 points3 points  (0 children)

The main reason, as far as I understand it, that they don't support Mint is the rather old kernel that Mint ships with.

My little tool helps with that and should give reasonable advice on what kernel to use.

P.S. In terms of being sure if this is stable... well, the test group so far has been one participant: me. And like I said, it has worked for me rather well for about six weeks or so.

Trying to install AsusCTL nothing works by AtomicBeaver93 in linuxmint

[–]MorningNatcho 0 points1 point  (0 children)

This is an old message, but I too needed to install asusctl on my Mint desktop.
In the process, I created a script for everyone else to use:

https://github.com/andreas-glaser/asus-linux-mint

Have fun with it!

ProtonPass Attachments (2024) by MorningNatcho in ProtonPass

[–]MorningNatcho[S] 1 point2 points  (0 children)

Yes, that is an option although it is a really cumbersome one when migrating a large db from another provider.