The & is an indicator to most shells to run this command in “the background”. Try and run ( sleep 10; echo hi ) & - you’ll see you get your shell prompt back, where you can run more commands, but 10 second later you’ll see that ‘hi’ come through. ‘blocking’ is the default behavior, if you don’t add the & you’re still going get the hi in ten seconds, but you don’t get a prompt because your shell’s execution is blocked until your command is done.

The doc here is indicating that you havea choice between autostart_blocking.sh and autostart.sh, the latter of which would be run with a &. They could have expressed this better.

As for why your script didn’t work, I’d try executing it in a terminal to see what error message comes up.

both mobile and desktop have the plaintext notes in a sqlite db. they’re “easy enough” to export if you’re bailing on the app, but not to regularly switch between two different apps

don’t forget to install gti

A JavaScript VM in the kernel is inevitable.

More than that, your editor doesn’t run with root permissions, which reduces the risk of accidentally overwriting something you didn’t mean to.

it feels to me, like they’re less looking for new people to start doing this “work”, but more to connect with people who already happen to be enthusiastically going to events and showing off their laptops.

Are you using PersistentVolumes? If your storage class supports it, looks like there’s a volume snapshot concept you can use, have you looked into that?

Not sure what you’re doing, but if we’re talking about a bog standard service backed by a db, I don’t think having automated reverts of that data is the best idea. you might lose something! That said, triggering a snapshot of your db as a step before deployment is a pretty reasonable idea.

Reverting a service back to a previous version should be straightforward enough, and any dedicated ci/cd tool should have an API to get you information from the last successful deploy, whether that is the actual artifact you’re deploying, or a reference to a registry.

As you’re probably entirely unsurprised by, there are a ton of ways to skin this cat. you might consider investing in preventative measures, testing your data migration in a lower environment, splitting out db change commits from service logic commits, doing some sort of blue/green or canary deployment.

I get fairly nerd-sniped when it comes to build pipelines so happy to talk more concretely if you’d like to provide some more details!

I use these two vim plugins for the same functionality without leaving $EDITOR:

• https://github.com/wookayin/fzf-ripgrep.vim
• https://github.com/ctrlpvim/ctrlp.vim

I’ve also started dabbling with using fzf in scripts for the team to use. Don’t sleep on the --query and --select-1 flags!

is that more or less cursed than cat image.img > /dev/whatever?

dd if=image.img of=/dev/disk/flashdrive is usually all you need

Definitely not what you’re talking about, but still: https://www.destroyallsoftware.com/talks/a-whole-new-world

The two factors at an ATM are possession of your bank card + knowledge of your pin. (it also takes your photo, for good measure)

GitHub will happily accept a smart card or whatever, if an extra plastic rectangle jives with you more than an OTP generator.

Your two factors shift to possession of your password vault + knowledge of the password to it. You’re okay IMO.

You also still get the anti-replay benefits of the OTPs, though that might be a bit moot with TLS everywhere.

just to give you the term to search for, these types of applications are called snippet managers. for example, https://snibox.github.io/

there’s a ton of them around. I don’t have a particular one that I recommend, since it’s not something I use in my workflow.

grep -r exists and is even more faster and doesn’t require passing around file names.

grep -r --include='*.txt' 'somename' .

Better than that, git config supports conditional includes, based on a repo URL or path on disk. So you can have a gitconfig per organization or whatever, which specifies an sshCommand and thus an ssh key.

yep. they’re still here. they got smaller, and we call them “tracking pixels” now.

it’s just an image, which, server side, you can count the number of times it got loaded. easy to embed and no js required.

just to add a little more explanation to what the other posters are suggesting… a hard drive, from the perspective of your OS is very very simple. it’s a series of bytes. for the sake of this example, let’s say there are 1000 of them. they are just a series of numbers.

how do you tell apart which numbers belong to which partitions? well there’s a convention: you decide that the first 10 of those numbers can be a label to indicate where partions start. e.g. your efi starts at #11 and ends at #61. root at starts at #61 and ends at #800. the label doesn’t say anything about the bytes after that.

how do you know which bytes in the partions make up files? similar sort of game with a file system within the bounds of that partion - you use some of the data as a label to find the file data. maybe bytes 71-78 indicate that you can find ~/.bash_histor at bytes 732-790.

what happened when you shrunk that root partions, is you changed that label at the beginning. your root partion, it says, now starts at byte #61 and goes to #300. any bytes after that, are fair game for a new partion and filesystem to overwrite.

the point of all this, is that so far all you’ve done is changed some labels. the bytes that make up your files are still on the disk, but perhaps not findable. however - because every process that writes to the disk will trust those labels, any operation you do to the disk, including mounting it has a chance to overwrite the data that makes up your files.

this means:

• most of your files are probably recoverable
• do not boot the operating system on that drive, or any other that will attempt to mount it, because you risk overwring data
• before you start using any data recovery tools, make a copy of the raw bytes of the disk to a different disk, so that if the tools mess up you have an option to try again

ONLY after that is done, the first thing I’d try is setting that partion label back to what it used to say, 100gb… if you’re lucky, everything will just work. if you aren’t, tools like ‘photorec’ can crawl the raw bytes of the disk and try and output whatever files they find.

good luck!

Hey, thanks for that, I appreciate you sharing your list.

One option you can consider with fairmail and gmail is to use an “app password” to authenticate to IMAP, instead of oauth. That might work better when backing up with neo backup?