yuubi

I think the latter. According to the decompression instructions in README.md, "The reads will NOT be in the same order as in the original file".

It sounds like it's meant results of DNA sequencing processes that produce sequences for random small pieces of the molecule.

A tar file doesn't have a central directory like a zip, so you do have to search all the file headers. However, each file header contains the length of the file it describes, which lets you seek past the content of any files you don't care about if the tar isn't stored in a way that would prevent seeking.

The 3 kV rating is most likely 3 kV on a human body model, which is a small capacitor (few picofarads) with a series resistor. This says nothing about what happens if you charge a large capacitor to 100v and then dump it through as low a resistance as possible into the victim port.

A lot of vendors do for recent processors. You can easily get a z80 datasheet, but not necessarily complete info for a recent ARM SoC.

You needed to add a receiver near the load. They had a couple of variations of a box with prongs on one side and an outlet on the other to switch plug-in devices and a replacement wall switch for other lights.

Yes, that looks exactly analogous, but my question is why people don't use the perfectly good built-in conditional termination in a while or for loop and instead add on an if statement.

(Also, I don't understand why a for(;;) loop is more attractive than a while(1) loop.)

Why? That reminds me of the

    while(1) {
        if (condition)
            break;
        ...
    } 

stuff I've seen too much of and can't explain, instead of just while(!condition) { ... }.

If the attacker doesn't have the private key that matches the Subject-Public-Key-Info, then he won't be able to impersonate your server given such a cert. (If he has, then there's no need to produce a replacement cert; the official one is good enough).

From the docs (but not actually messing with any actual parts), it looks like the 8266 has an IPv4 stack in ROM.

For a vaguely similar use case (repeat till host is up) I once wrote

    until ssh ...; do sleep 5; done

which stops looping once a connection succeeds.

An inode, traditionally, is the per-file data structure on disk (or in memory) that contains the user/group IDs, file type (plain/directory/device/etc; not jpeg/png/executable/etc), permissions, file size, and the location of the content (either a list of block numbers, or the address of a block containing the list if it wouldn't all fit into the fixed-size inode), among other things. These structures were identified by a number. This is an implementation detail not specified by POSIX.

A directory, historically (on systems with 14- or 30-character file name limits like we had in the 1990s, at least 4.2 or 4.3 BSD-derived), consisted of a file containing a list of (16-bit inode number, file name) structs, thus making a nice round 16 or 32 bytes per directory entry, evenly dividing a 512-byte block. On some older systems you could see this structure by opening and reading a directory with open and read (I think every system everywhere prohibited writes to a directory because modifying a directory would allow you to access files in unreadable directories, uncleanly delete any file given its inode number, etc). The only special thing about a directory on disk was that its inode said it was a dir, so the filesystem code would trust it as a source of inode numbers and otherwise use it as a dir.

Some of the 14-byte-name systems supported symlinks. As there was no space in the directory entry for anything other than an inode number, the link contents would have to be accessed through an inode. (I think I've heard of systems that could store very small file contents like typical symlink target names in the inode instead of allocating a data block, but can't name one).

The number you see in ls -i, which is sometimes called just the "inode" (and apparently also called the "file serial number"), is the number in the directory entry that's used to find the inode. I guess someone somewhere had or intended to have a system that could store symlinks in the directory instead of consuming an inode.

> Is it possible to have a password that you don't even know?

Seemingly, yes, according to https://www.usenix.org/conference/usenixsecurity12/technical... , which has a paper I read a while ago and a video I never got around to watching.

Abstract:

Cryptographic systems often rely on the secrecy of cryptographic keys given to users. Many schemes, however, cannot resist coercion attacks where the user is forcibly asked by an attacker to reveal the key. These attacks, known as rubber hose cryptanalysis, are often the easiest way to defeat cryptography. We present a defense against coercion attacks using the concept of implicit learning from cognitive psychology. Implicit learning refers to learning of patterns without any conscious knowledge of the learned pattern. We use a carefully crafted computer game to plant a secret password in the participant’s brain without the participant having any conscious knowledge of the trained password. While the planted secret can be used for authentication, the participant cannot be coerced into revealing it since he or she has no conscious knowledge of it. We performed a number of user studies using Amazon’s Mechanical Turk to verify that participants can successfully re-authenticate over time and that they are unable to reconstruct or even recognize short fragments of the planted secret.

> chemical resistance

I remember from a freshman chem lab that trying to dissolve aluminum into acid doesn't work because acid promotes oxide growth, so we dissolved it in NaOH, which was supposed to attack the oxide, then acidified the solution. Are the aluminum oxide minerals similarly susceptible, or do they also resist alkali?

> fixed-width numeric types

uint32_t and friends instead of the implementation-defined unsigned int/long.

See http://pubs.opengroup.org/onlinepubs/007904975/basedefs/stdi... for many details (including things like the name for "the fastest signed integer type with at least 8 bits", which could be signed char on machines that support byte access in hardware and signed 32-bit on machines where byte addressing means loading a word, bit-bashing the new value in, and storing it back).

Aluminum exposed to air very quickly grows a thin passive layer of aluminum oxide (unlike steel rust, this layer is stable). Anodizing forces it to grow a thicker layer.

Aluminum oxide is hard stuff: 9 on the Mohs hardness scale (talc = 1, diamond = 10). https://en.wikipedia.org/wiki/Mohs_scale_of_mineral_hardness

If they have reasonable suspicion that a crime happened or is about to, sure. However, reading a book other than, say, _How to hijack an airplane_ isn't that.

Unwanted attention from someone who won't take "leave me alone" for an answer normally counts, even in a situation where the target is allowed to walk out and knows that nobody involved in the unwanted attention is armed, even if the target knew for a fact in advance that the attention would end in 10 minutes.

In normal power distribution, much of the cost is in generating the electricity, and the cable is cheap and readily accessible and you can easily take several truckloads of heavy cable to the many sites.

Undersea cable is different, and I suspect that nobody cares if 99.9% of the power is wasted to heat the power wire as long as enough gets to the repeaters.

Kirchhoff's law says that if your wire is insulated, ask the current that goes in one end comes out the other. The only thing is that you need to provide sufficient voltage to push it through the long wire.

A IP protocol that was neither TCP nor UDP nor SCTP.

> trying to beat C into a form that does IPC protocol-handling well.

The opposite worked at least once: have Erlang code deal with C-friendly structures.

Last time I got to work on an Erlang project, we needed an external C program to do some network stuff we couldn't do in Erlang. We just defined a simplistic protocol easy to parse from C, with {packet, 4} framing (each message was preceded by a 4-byte length) wrapped around the messages. Pretty much any format easy to parse or generate in C is trivial to deal with in Erlang.

Conveniently, the retail price includes the direct expenditures on energy to make and transport the item to the store.

I recall the electricity rate being around 0.08 USD/kWh around here a while back, so 1000h of 100W consumption would cost $8. I don't remember exactly what 100W plain light bulbs cost, but it certainly was a lot less than that.

10M thick Ethernet also had vampire taps and cable (about 1/2 inch diameter) with marks on it.

And design transponders so they never go wrong and need to be turned off, and electrical supplies that never need to be turned off, and electrical generators and transfer switches that never go wrong such that shedding the load of the transponder is useful in an emergency, and redesign the parts of the radar system that assume that pilots turn off their transponders when nearby.

Sometimes N=9, such as when the address starts 00:50:c2. This block is divided into blocks of 4096 instead of the usual 2^24 so small users can get a block for a few hundred dollars instead of over a thousand.

A ban on LTE over 5 GHz seems a bit heavy-handed and prone to allowing further abuses (as some dude on IRC said about something else, it's like trying to kill a mosquito with a chainsaw: you end up all bloody and probably don't even get the mosquito).

I think the real objectionable part is the requirement that the 5 GHz band be restricted to "licensed-assisted operation", only as a secondary downlink for a system based on a licensed band. A rule that any system using unlicensed spectrum shall not depend on licensed spectrum would block the existing LTE-on-5GHz plan and either get the whole idea scrapped or get mobiles that can work entirely on unlicensed spectrum into the market, opening up the possibility of private LTE networks on unlicensed spectrum.

Given how important centralized choke points seem to be to the 3GPP architecture, I tend to suspect it would just chase licensed users completely off the unlicensed spectrum.

Buy phone, claim it's locked/blacklisted, return locked/blacklisted phone, get refund, profit?

It's worse than parent makes it sound: the conduct in that case was growing grain without permission, not for sale, but to feed to chickens on the same farm.

The two US stores I've seen have kept one cart after the cashier. When done checking out, you take the newly full cart and leave your empty there for the next customer.

> why the dead weight?

I assume it's because masses are more stable and easier to calibrate than the gauge on a hydraulic press.

> did people ever voluntarily use csh?

Yes, for an interactive shell, back when the choice was between csh that had command-line history and sh that didn't.