Thanks for that. I was unaware that is how it worked.
Thanks for that. I was unaware that is how it worked.
removedant?
lol
He had six children. fuck.
Syncthing may fit the bill.
I went from a T480 to an 11th gen Framework and while I appreciate the upgradable design and better portability, honestly, I could have easily continued to use that Thinkpad as my main machine. If you don’t need the upgrade, save your money and drive that T480 into the ground. It’s a fantastic machine, as is the Framework.
Yeah it is but it’s a pretty capable laptop. I’ve replaced mine with a Framework 11th gen for my daily use but my T480 is currently hosting 10 VMs for my homelab. It’s got the base CPU, i5-8250U, 64GB of RAM and a 4TB SSD and is plenty of horsepower. I really only got the Framework because I was excited about the product and company, not because I was unsatisfied with the T480. I highly recommend it.
Credit should go to Nathan Pyle where this content originated with a less insane font.
Not sure if you’re into command line tools but I’m using hledger and have emulated pretty well the YNAB envelope method and I’m liking it quite a bit. Using plain text for transaction journals is amazing and has solved some of the ambiguity I felt when using YNAB. Tons of information here for this type of accounting method. And look here specifically for implementing the envelope method with these sorts of tools.
No phone apps are available as far as I know but depending on your technical expertise you could provide reports from a webpage pretty easily.
Can you paste the line from ls -l? Sanitize the username/date/time if you need to. Example:
-rw-r–r-- 1 bolapara users 0 Nov 21 17:19 asdf
OK I see. Can you create a new file with nano and then do an “ls -l” so we can see the permissions it’s given? Also provide the output of the command “umask” as the user you’re working with.
Can you be more specific about what you mean by this: “gives (the file) elevated privileges”?
Really looking forward to people sharing their experience with Linux on the AMD Framework!
This is almost certainly the result of accidentally letting the passwords get into the logging infrastructure.