When you copy /home make sure you get the “hidden” files. They start with a “.” and some programs ignore them by default. That’s also where most configuration files are.
Check out rsync -avz
When you copy /home make sure you get the “hidden” files. They start with a “.” and some programs ignore them by default. That’s also where most configuration files are.
Check out rsync -avz
I’m far from an expert on NixOS but using another package manager with nixos seems like it would defeat the entire purpose of the distro. It really seems like you must be ok with creating your own packages.
Here is how you create a package: https://nixos.wiki/wiki/Nixpkgs/Create_and_debug_packages
However - it’s hard to tell but flakes seem to be the emerging standard. Here is the documentation on flakes: https://nixos.wiki/wiki/Flakes
To answer your other question services are part of packages. For example here is NFS: https://github.com/NixOS/nixpkgs/blob/nixos-23.11/nixos/modules/services/network-filesystems/nfsd.nix
More examples can be found here:
Auditing is nothing more than reading the code. Give it a read and make sure you understand everything it’s doing.
This is a great lesson on trust as well. I can tell you I did an audit and it all looks good but does that really have any value?
Ive heard ikea bulbs were pretty good.
Something else to think about - after moving to a new apartment I switched from smart bulbs (hue) to smart switches (Lutron casetta). It seems pricy but since one switch controls multiple bulbs here (4 in one instance) the price difference was negligible.
I’ve lost the ability to set colors but that was always a gimmick for me and Casetta has been even more rock solid than hue.
I’ll join in. Just signed up for the trial of Kagi after seeing an article on here and I’ve already subscribed. I don’t miss google at all and am excited to play with some of the innovating features (lenses look neat).
Funny. I have some Disc Lite 5s that I’ve yet to get going due to difficulty of setup. We did have plans of a little Wi-Fi mesh setup to setup a WAN.
This would just be for fun between a few friends and the price point is pretty attractive. Plus the ham in me is a little excited about messing with antennas.
Dude this is a great response. I’ve spent the last hour trying to piece together how it works and you nailed everything perfectly.
I’m a ham so familiar with radios and have been trying to setup some Wi-Fi links between friends but this seems a little more practical.
Is a few mile range possible with houses etc in the way? We’re all about a mile away from each other, although I may throw an antenna on top of my house (maybe 10m up)
The documentation is a little lacking. What exactly is the range of each decide? I see the record of 100+ miles but can I easily connect people within a few miles?
What exactly does this do? Is it just a messaging app?
Linux has directories (folders) that contain programs. The two major conventions are /bin (short for binary which is another name for an executable program) and sbin (system/super user binaries).
Kbin seems like a play off of that, don’t know what the k implies tho.
This is a good post.
As for why people don’t like systemd, it follows the kitchen-sink approach to software and does a lot of things at once.
For people new to Linux I just want to point out - for better or for worse this goes against the Unix philosophy.
Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface.
I have firstnamelastna.me. Can you get a little creative with the TLDs?
To answer your question tho hello@firstname.com would look better than Lastname@firstname.tld
You can also do a catch all and use anything@firstname.com (eg google@firstname.com) but those get a little spam happy.
I just looked at most (if not all) the apps I have. They all had the option to select what you see by default.
It’s easy! Don’t. It’s not possible to do.
Focus on one small area instead of the whole project. If there isn’t a “beginner” ticket selection then find one (or give yourself a goal). Figure out where that code is and start playing around with it.
As you branch out and work on more and more tickets you’ll gain more and more experience. You’ll understand how different blocks and systems interact and gain a better overall understanding of the code base in general but you’ll never be able to keep everything in your head. It’s just not needed.
And I don’t think it’s been said yet but as a former vi guy a good IDE was a huge boost to productivity. Ease of navigation around the code, intelligent searching, etc really helped out in the exploratory phase.
Holy Necro….since I’m here tho I think kbin is more set up with this. It has a microblog section although I haven’t really explored it.
I wound up with gollum. Git based with a wiki format. Works well enough for my limited use.
https://github.com/gollum/gollum