understood. tinycore is a live installable distro, so you can still test it on bare metal.
pick the GUI flavor and kick the tires for a while.
…just this guy, you know.
understood. tinycore is a live installable distro, so you can still test it on bare metal.
pick the GUI flavor and kick the tires for a while.
the repos are browsable inside the package manager - I would imagine they are browsable outside as well, but I have never had cause to do so.
honestly, give tinycore a shot. fire it up in a VM and take a look around - it really is an amazingly useful distro.
if the install had finished and the installer was simply reading the flash drive to clean itself up, unmount filesystems and reboot, then chances are you are fine. However, as a personal rule I never allow an installation to go into production if there were any unexpected anomalies during installation. its just not worth the risk.
only lwn can make an otherwise lukewarm mailing list kerfuffle a riveting read. love me some lwn.
I understand caution when approaching things like secure boot - it can absolutely be abused by monopolies. however… barring inherent or implementation flaws and ensuring that signing keys are under user control it conceptually (and practically) allows for some useful things.
a good, quick read. one of the linked articles[1] at the bottom of TFA is excellent.
soooo… I started skimming the article, took a look at its length and almost noped out. but it was too late. I was sucked into a long and interesting read.
agreed. EXT4 for system, XFS for everything else (mostly large VM image files). when XFS is properly configured for the underlying drive array geometry, its a nearly perfect streamlined FS.
?! - this has gone beyond annoyance. your OS actively hates you. this is an abusive relationship, my friend.
deleted by creator
deleted by creator
deleted by creator
according to the HN comments, many dentists seem to be familiar with them - so likely see your family dentist.
there is also quite a bit of debate over (problematic) changes to your jaw alignment and bite through usage of these things, so be aware of this and get legit medical advice before you decide to make use of one.
deleted by creator
ZFS hits memory hard and sometimes can bring out latent deficiencies in that hardware. on non-optimal hardware its a bit of a hardware torture test in its own right.
having said that, EXT4 and XFS are wonderful unless you need zfs/btrfs.
if you are self hosting and enjoy over-engineering systems… VLANS, ACLs between subnets and IDS/IPS should be part of.your thinking. separate things into zones of vulnerability / least-privilege and maintain that separation with an iron fist. this is a great rabbit hole to fall down if you have the time. however, given a skilled adversary with enough time and money, any network can be infiltrated eventually. the idea is to try to minimize the exposure when it happens.
if the above is not a part of your daily thinking, then don’t worry about it too much. use a production OS like Debian stable, don’t expose ports to the public internet and only allow systems that should initiate communication to the internet to actually do so (preferably only on their well known protocol ports - if possible).
this is a great bit of advice here. KVM with GPU passthrough is magical when you get it working. excellent comment.
the article and HN discussion were not bad, actually. its not often I get to poke a Senegal domain, but (with proper web browser prophylactics) adventure… ya know!
a really good article. well worth the read.