How does a disaster recovery plan with it look like?
sudo mknod /dev/null c 1 3 && sudo chmod 666 /dev/null
/dev/null is an ACID compliant database
81–90 of 203 posts
Re: /dev/null is an ACID compliant database
#82/dev/null is not a database. By this logic is a hard disk a database, is a CD a database. No. They are storage mediums. You could store a database on them, but they themselves are not a database. Considering there is no way to read back data written to /dev/null it will not be useful for storing database data.
You can store any data as long as it doesn't contain any ones
And, you don't depend on it remembering how many zeros you wrote last.
Re: /dev/null is an ACID compliant database
#83I love this
Re: /dev/null is an ACID compliant database
#84I guess /dev/null is also an excellent source of investment advice, you are guaranteed to not lose money
Re: /dev/null is an ACID compliant database
#85Re: /dev/null is an ACID compliant database
#86Always instantly consistent, always available, and perfectly tolerant of partitioning. Truly, it is the only database which can be scaled to unlimited nodes and remain fully CAP.
Not just instantly consistent on one machine, but globally sharded all across the universe.
Re: /dev/null is an ACID compliant database
#87"The system transitions from one valid state to another" is clearly false: the system only has a single state.
One of the first state machine you'll ever learn about in undergrad permits transitions from a state back to itself, so I don't see this as a barrier.
And you can implement /dev/null with multiple states, as long as you make them all behave the same way.
Re: /dev/null is an ACID compliant database
#88Earlier quoted context omitted.
Interestingly I tried this as well and was disappointed with the results: yes $(printf %1024s | tr " " "y") | pv > /dev/null About the same throughput as letting yes output a single character. I guess Unix pipes are slow.
> I guess Unix pipes are slow. Or string concatenation, or pipeviewer.