Where bitmap is a Python long, consider the innocent looking Pythonexpression:

bitmap = bitmap & ~(1L << bit)

This is the perfectly normal way of clearing a bit in a bitmap, soit looks like there's nothing peculiar going on here.

Except that Python longs are of indefinite (and theoretically infinite)length, and what makes this expression work in normal integers is thatthe two pieces have the same (finite) size. So Python is clearly notjust doing straight binary operations here

Most archive formats, such as tarballs, cpio archives, and zip archives,interleave the file names (and their directory structure) with the filecontents. The dump filesystem backup program such as Solaris ufsdump do not. The dump archive format starts with an index that has all of thefilenames and the directory structure; after this comes the actual filecontent, labeled by inode number.

This has an important consequence for detecting damaged archives. In aninterleaved format like a tarfile, getting a full file listing requiresreading the

I think that universities not having a return on investment as such may go at least part of the way to explain someweird university behaviors around staff. The core issue is that withoutan ROI it becomes difficult to see the cost of how staff spend theirtime.

(With a ROI for projects it is easy to see how having staff spend theirtime on a lower-ROI activity more or less directly costs you money.)

Not only does this effectively make staff into a constant sunk costregardless of what you have

Normally, one of the things RPM bases dependencies on is package names.The problem with doing only this is packages that want to depend oncapabilities instead of specific packages; for example, that there issome mailer installed, not specifically that Sendmail is installed. Todeal with this, RPM introduced the Provides: directive, which lets anRPM package tell the overall RPM system that it is providing somethingthat is not obvious from its name, its files, and so on.

In implementing this, RPM has chosen to