What about Dubai, the city built almost entirely by slavery? That's a libertarian paradise right there. As long as you have money you can do pretty much anything you like and get away with it. Well, money and a penis.

It's nice to see you support your dad, but nobody else shares your bias.

Oh, never mind. I thought you were here to support your dad. Is he lazy or incompetent?

The USPS scans every single piece of mail which passes through a sorting facility. One of those lazy, incompetent postmasters told me (about a month before the revelation that the USPS was handing all this data to the feds) that they simply threw that data away when they were done with it, and that this was the reason that they couldn't give you any information about where your first class mail had been in its lifetime. But in actuality, none of that data has been thrown away, and only laziness and incompetence prevent giving you this information while it is still new and held on near-line storage.

The point is that it only takes a handful of nefarious fucks to hand all of that data over to the government for interpretation without a warrant. And that is what the USPS does; they hand all information on all mail that they route directly to the federal government, probably via the DHS now which is actually its job: tying together disparate law enforcement agencies.

It's too bad that police discrimination and abuse aren't hot-button issues for Arizonans, who apparently enjoy living in a police state.

Almost. Because some MBA at GE decided to put the plant where it needed to not be placed and the US government forced that location over the protests of the Japanese, the generators (which were not skipped) were flooded and could not function. You could also pin it on the Japanese failure to elevate the generators, which was considered undesirable because of aesthetics. But you can't blame it on skipping the generators, because they had generators. They were simply worthless due to site selection.

These engines have been sitting around packed in oil or whatever ;) What evidence is there that they were ever spaceworthy? Did they subject every critical part to X-Ray inspection, etc etc? Even that can't detect some kinds of defect.

It seems to me that in order to be better, they have to deliver their payload, and not explode. When they blow up, their effectiveness falls off to zero real quick.

I can't use several of my machines because of lack of drivers for horribly common hardware which is nearly identical to supported hardware and for which a fix has actually been submitted on the mailing list. In spite of it being only some changes in values and not in the basic functionality of the driver, they begged off adopting the changes because of concerns with Linux copyright, which has already been shown to not apply in this case. Just NIH. Well, fuck 'em. I'll use something with some support.

That's basically already the case, their hardware support is pisspoor. Which is okay if you're building a machine around openbsd, who cares? But it's a bummer if you want to use what you have lying around.

I don't think someone who focuses on science can combat these religions. It has to be someone who's devoted their life to studying each one, and who knows where all the problems are.

But if I were going to take the approach from science, I would do what the religious people do, and just refer back to some prior time when someone argued about this and claimed victory, then I'd dance around and claim victory for myself. Because what else can you really do when you're arguing with someone whose arguments are provably stupid?

That's a feature. Typical operating systems around when Unix were developed had structured files understood by the operating system. We can still have that sort of thing, through libraries, and indeed some applications make use of them. But not forcing it on applications leaves them free to implement their own backstores.

Many applications don't need to make use of a complicated configuration file format, and there are other real-world reasons not to conform to a system standard, such as cross-platform applications. Sometimes it's just not worth it to make all the changes to make your app a good citizen. And that's why all modern operating systems have the concept of unstructured files.

It's not that, it's just that those people flock to Linux because they see it as the new shiny, forgetting that it is in fact emphatically the opposite. It's a macrokernel reaction to a microkernel operating system! It's actually a new implementation of the old faithful, which is why this kind of crap is so frustrating to the rest of us in the Linux camp. Linux is not the new hotness, it is the old way. If they want to crap up something with new daemons maybe they should join the HURD

Wait, what?

Sure it can. It's called double locking.

Wait, what? Impossible? You don't seem to understand what scripts do.

Do you ever say anything true?

Uh what? HAHAHAHA. And also HAHAHAHA.

Let's actually discuss what you just said here.

Journald doesn't spit out text log files, that's the problem.

It will spit out text log info to another syslogd, which means there's more latency before the log message hits the disk.

Therefore you can not get simultaneous logging.

If journald did text logging, which a Unix syslog should do (it is the Unix way to use human-readable flat text files and that is for a good reason) then no one would be bitching. Text logging is more important than binary logging, it should be first.

Nobody in the systemd camp seems to be able to remember that flat files without specific formats was an advancement of Unix. Let the application sort it out, and simultaneously make the information meaningful to humans.

The GNOME project is going to do that itself, the dependency on systemd is temporary, or so they claim. It has to do with Wayland, IIRC. So all Debian has to do in order to solve this problem is wait for GNOME to pull its head out (like usual)

You are mischaracterizing the argument, which is that text logging is a second-class citizen. No one claimed that it was not possible to have text logging if you are using systemd. The claim is that in the lag between systemd binary logs and the time when systemd has bothered to hand the message off to the next systemd and it gets written to disk, you can lose messages from your text logs that may or may not be in your systemd log due to truncation of the binary log in the case of a crash, and this is a fact. Know what else is a fact? Nearly no one who is bitching about binary logging would be doing so if it were added on to syslog rather than replacing syslog with its venerable and functional text logs which we can read from the filesystem with a disk editor if necessary.

There was no need whatsoever to make a new logging daemon which is integrated with a new init daemon if the goal was to implement binary logging. Because of the modular nature of Unix, it is possible instead to simply change the log daemon. And it was further completely unnecessary to make text logging a second-class citizen to binary logging. And it is further possible for them to fix this by implementing text logging, but NIH so nyah nyah nyah, our way is the right way and your decades of experience mean nothing. Right? Your side mischaracterizes the debate and ignores the lessons of history.