A good solution to the remote-admin by email are fetchmail and procmail. Plus, i know it's out of fashion, but a working MTA, if you care about the box replying.
That's not a meaningful thing to say. Time began with the Big Bang (as per the standard model). It's like asking what's 1m to the north of the north pole
Yeah, i agree, software wear and tear is a bitch. After 15 years of continued use, i reckon most of the 0s are cracked open, and the 1s are likely entirely dull.
How is that a point? Yes, it's a design decision, obviously it's one. So what? Weren't you trying to point out why in your opinion database-stored configuration is superior over text files -- i.e. why you think the design decision should be done in favor of binary files? BTW in the unix-like world, the UNIX philosophy gives a pretty definite rationale behind the design decision made in this context. Please, take the time and read this
Your arguments still don't make sense at all, therefore this will be me last reply.
At first, you claimed a replicated database was more reliable than a non-replicated hard disk. Note how your argument is replication vs no replication, not files vs database files.
Now you're arguing that manual configuration editing is inferior to a configuration server, again it's not about text files vs database files, but manual vs automatic.
People talk about text files like they're magical and more robust. The fact is that in order to access a text file you need about 14 pieces of software, and for one of them you have a lot of options as to which piece of software you use. If it is in a binary format you need about 14 pieces of software, and you have less choice about that one piece.
Are you trying to disprove your own point now?
Your reply addresses zero of my arguments. Try again.
I've yet to see a standard text file editor which is able to view a text file in/etc without the aid of a very non-standard filesystem driver.
What kind of retarded straw-man or obvious troll is that? Where do you think databases store their data? In the magic data cloud? Besides, what does the 'non-standard' part even *mean*?
Besides, when your hard drive crashes it is pretty hard to read the text files on it. On the other hand, when the configuration is stored in a replicated database, your cluster can keep on chugging along.
If the hard drive crashes, data may be lost. If the data is stored redundantly, data may be safe. News at 11.
Seriously, where to you *think* databases store their data? On a side point,/if/ your hard drive crashes, the odds of recovering text files from the mess are way better than recovering database data files, as they are/way/ larger and more complicated.
Even most admins who love text files in/etc stick them in non-text repositories like git just to manage things.
Really, it's beyond embarrassment. Git by its very nature *deals with* text files.
But yes, I am a systemd proponent.:)
Of course you are.
You'll be happy that it [tl;dr]
I really don't care. I abandoned Linux in favour of the BSDs when it started to smell, and you're the perfect example of why it does that nowadays
Something tells me you're also a systemd proponent. It's about simplicity, and therefore flexibility. If/etc becomes a database, you lose the ability to use your standard tools on it, which, gasp, tend to work on text files, because it's the one single truly universal/and/ human-digestable format.
Slashdot Mirror
As long as the computer is somehow able to play it, there's nothing to stop me from intercepting the audio stream at the very end.
A good solution to the remote-admin by email are fetchmail and procmail. Plus, i know it's out of fashion, but a working MTA, if you care about the box replying.
[...] to a date with pizza [...]
/. -- where guys date pizza,
Ternary.
> if (a = b) assigns the contents of b to a and executes the code following if b 0. Who the hell thought that would be a good idea?
There are indeed times it is useful but I 100% agree, using the _same_ syntax as assignment was full retard.
The same syntax as what exactly? = is just assignment, nothing else.
They should of used:
You should of used "have". And your proposal is utter crap.
At the moment before the Big Bang
That's not a meaningful thing to say. Time began with the Big Bang (as per the standard model).
It's like asking what's 1m to the north of the north pole
Did that. Not regretting it.
Yes! Where? I want it!
Son, there's no point in asking this. It's commonly agreed upon that they are a miracle.
No that'd be minix. NetBSD is just for people who like a sane system without any Poettering-crapware, and oh well, see sig.
It's Linux. It's always Linux, because hey, Linux is a kernel. The kernel. /THE/ Kernel.
...written on my NetBSD machine.
No, it didn't say rresearchers anywhere in TFA.
Do it right, at least.
board.
I recently stopped using AdblockPlus, for Ghostery+NoScript+Flashblock already block everything ABP would block otherwise
Yeah, i agree, software wear and tear is a bitch. After 15 years of continued use, i reckon most of the 0s are cracked open, and the 1s are likely entirely dull.
How is that a point? Yes, it's a design decision, obviously it's one. So what? Weren't you trying to point out why in your opinion database-stored configuration is superior over text files -- i.e. why you think the design decision should be done in favor of binary files?
BTW in the unix-like world, the UNIX philosophy gives a pretty definite rationale behind the design decision made in this context.
Please, take the time and read this
All your base are belong us!
You're doing it wrong.
I tried, but all i got in return were straw-men. Not even well-thought-out straw-men.
I'm polite enough, i even said "please".
If you feel like discussing the matter at hand, start by considering the points you've ignored until now in this conversation.
NetHack, preferrably on a public server
Years of time can be wasted
Look, there are over 9000 memes, but your list doesn't contain any.
Your arguments still don't make sense at all, therefore this will be me last reply.
At first, you claimed a replicated database was more reliable than a non-replicated hard disk. Note how your argument is replication vs no replication, not files vs database files.
Now you're arguing that manual configuration editing is inferior to a configuration server, again it's not about text files vs database files, but manual vs automatic.
Please try to become a little more competent.
People talk about text files like they're magical and more robust. The fact is that in order to access a text file you need about 14 pieces of software, and for one of them you have a lot of options as to which piece of software you use. If it is in a binary format you need about 14 pieces of software, and you have less choice about that one piece.
Are you trying to disprove your own point now?
Your reply addresses zero of my arguments. Try again.
cool dupe bro
I've yet to see a standard text file editor which is able to view a text file in /etc without the aid of a very non-standard filesystem driver.
What kind of retarded straw-man or obvious troll is that? Where do you think databases store their data? In the magic data cloud? Besides, what does the 'non-standard' part even *mean*?
Besides, when your hard drive crashes it is pretty hard to read the text files on it. On the other hand, when the configuration is stored in a replicated database, your cluster can keep on chugging along.
If the hard drive crashes, data may be lost. If the data is stored redundantly, data may be safe. News at 11. Seriously, where to you *think* databases store their data? /if/ your hard drive crashes, the odds of recovering text files from the mess are way better than recovering database data files, as they are /way/ larger and more complicated.
On a side point,
Even most admins who love text files in /etc stick them in non-text repositories like git just to manage things.
Really, it's beyond embarrassment. Git by its very nature *deals with* text files.
But yes, I am a systemd proponent. :)
Of course you are.
You'll be happy that it [tl;dr]
I really don't care. I abandoned Linux in favour of the BSDs when it started to smell, and you're the perfect example of why it does that nowadays
Something tells me you're also a systemd proponent. /etc becomes a database, you lose the ability to use your standard tools on it, which, gasp, tend to work on text files, because it's the one single truly universal /and/ human-digestable format.
It's about simplicity, and therefore flexibility. If