Well yes, humpback whales reach sexual maturity by around 10 years of age (some much before then it seems). A marine biologist is still practically in it’s larval form at that point.
(Yes, yes, I know that wasn’t what you meant, but I couldn’t help myself)
I was more suggesting that it might be a bit eldritch, but sometimes humor doesn’t come across quite right/
The linked paper is focused on studying the ‘perforation-type anchor’ they use to hold the tissue to the mold as it grows, rather than keeping it alive afterwards. During growth the tissue and mold were submerged, or partially submerged, in a suitable medium to keep the cells healthy, and it was only when the resulting models were tested that they were removed (although one test did seem to involve letting it dry out to see if the anchors held). Growing the various layers of cells seems to be a solved problem, and I suspect that includes keeping them supplied with nutrients and such, so the authors aren’t examining that. What’s not solved is how to keep the tissue attached to a robot, which is what the authors were studying.
Do you really want to know? There are some things that the human mind is not meant to contemplate.
Take to another level by attaching a speaker to a PWM peripheral, now you can debug by ear, whilst driving your colleagues barmy with the beeps. The only tricky bit is working out if it was three beeps and a boop, or two beeps then a beep-boop.
There’s an easier and more reliable way to limit replication; don’t hive them the means to create a small but essential part, and instead load the first probe woth many copies of it and have each replica take a set percentage.
For instance, have the probe able to replicate everything but its CPU, and just load up a rack of them on probe 0. Every time it replicates itself it passes half of its remaining stock to the replica and they both carry on from there.
Crabadile - the ultimate lifeform.
This seems like a very complicated way to achieve your goal! It sounds like sitting yourself down and giving you a stern talking to might be a beter aporoach.
Having said that, if you have these very important files that you don’t want to lose, please make sure they’re backed up somewhere off of your machine. Storage fails, and it’s a horrible feeling losing something important. Unfortunately doing so would defeat the approach you’re thinking of.
This might be a case of needing to reframe the question to get to the cause of the issue, and then solve that. So, why do you want to make it hard to reinstall your machine? Is it the amount of time you spend on it, the chance of screwing it up, needing it working, has it become a compulsion or something else? Maybe if we can get to the root of the issue we can find a solution.
With regard to TPM, it’s basically just a key store, so you can use it fir anything really, althought it’s normally used by generating a TPM key and using it to encrypt the key that’s actually used to encrypt your data, storing the encrypted key with the OS. Just reinstalling won’t wipe the TPM, but unless you made an effort to save the encrypted key it’ll be gone. Given your problem statement above it just adds to the data you’d need to save, which isn’t helpful.
Ok, I’m still not clear on exactly what you’re trying to achieve as I can’t quite see the connection between somehow preventing certain files being duplicated when cloning the disk and preventing yourself from reinstalling the system.
Bear in mind that reinstalling the system would replace all of the OS, so there’s no way to leave counter-measures there, and the disk itself can’t do anything to your data, even if it could detect a clone operation.
If what you’re trying to protect against is someone who knows everything you do accessing your data, you could look to use TPM to store the encryption key for your FDE. That way you don’t know the password, it’s stored encrypted with a secret key that is, in turn, stored and protected by your CPU. That way a disk clone couldn’t be used on any hardware except your specific machine.
Nothing can prevent a disk clone cloning the data, and there’s no way to make something happen when a disk is cloned as you’re not in control of the process.
If you wish to mask the existence of the files, use either full disk encryption, in which case cloning the disk doesn’t reveal the existence of the files without the decrypt password, or use a file based encrypted partition such as veracrypt in which case the cloner would just see a single encrypted blob rather than your file names.
Ultimately encrypting the files with gpg means they have already effectively ‘destroyed or corrupted’ themselves when cloned. If you don’t want to reveal the filenames, just call them something else.
If you could be a bit more specific about your threat model people may have better ideas to help.
It sounds like you’re actually more concerned about the data in the files not being able to ‘pop up’ elsewhere, rather than the files themselves. In thus case I’d suggest simply encrypting them, probably using gpg. That’ll let you set a password that is distinct from the one used for sudo or similar.
You should also be using full disk encryption to reduce the risk of a temporary file being exposed, or even overwritten sectors/pages being available to an attacker.
This is an approach to life sentences I’ve considered before; I would suggest the prisoner could only petition for execution after being incarcerated for a significant period (20 years or so maybe?) and having exhausted all possible legal appeals. The delay is there to ensure it’s not a decision taken in desperation and haste. By that point, if any new evidence to exonerate them is going to turn up, it probably has, although I acknowledge that’s not always the case.
I’m not sure I’d equate it to voluntary euthenasia as the prisoner isn’t leaving jail alive either way. On the other hand, I can see why linking the two makes sense too.
Putting a simple preseed file on a debian install image is probably going to be your best bet. Assuming you can run a VM on your current machine it shouldn’t be too difficult to test it until you’re happy with it.
I just wanted to say ‘well done’ for going over what you said, realizing how it could be interpreted adversely, and admitting it. Not enough people are willing to do that, so well done!
It’s going to be a balance between your time getting an automated approach to work and the cost/effort of getting a monitor. Getting preseed working can be a bit fiddly, but it does mean you’ve learnt a new skill, getting a monitor sounds like it’ll be a pain, and you might only need it once.
Yes, that’ll work too, it does involve adding the disk to your machine temporarily though, so just be carefully which disk you format to do it. Please don’t ask why I say that, it brings back painful memories…
So you’re willingly admitting that you deliberately increased the chance of Trump winning by not voting tactically? I know it’s a rotten system, but you have to work with what’s in front of you. The approach you espouse makes it look like you’re actually a right wing saboteur rather than anything left wing.
While I agree with most people here that finding a keyboard and screen would be the easiest option, you do have a couple of other options:
Use a preseed file A preseed lets the installer run completely automatically, without user intervention. Get it to install a basic system with SSH and take it from there. You’ll want to test the install in a VM, where you can see what’s going on before letting it run on the real server. More information here: https://wiki.debian.org/DebianInstaller/Preseed
Boot from a live image with SSH Take a look at https://wiki.debian.org/LiveCD in particular ‘Debian Live’. It looks like ssh is included, but you’d want to check the service comes up on boot. You can then SSH to the machine and install to the harddrive that way. Again, test on a VM until you know you have the image working, and know how to run the install, then write it to a USB key and boot the tsrget server from that.
This all assumes the target server has USB or CD at the top of its boot order. If it doesn’t you’ll have to change that first, either with a keyboard and screen, or via a remote management interface sych as IPMI.
Tried with ‘Connect for lemmy’ against lemm.ee and just got a full screen error that vanished after a second.
/ etc / passwd <- so none of the components are blocked.
Take pride in the favt that even when you try, and think you’ve gone too far, your attempt is still so far above the word vomit he produces.
‘This post is a palaeontological disaster’ is a marvelous turn of phrase, and I intend to steal it for use at the first opportunity.