From one perspective, ideally SSL would be split apart into encryptionand trust, with the goal of letting you have encryption withouttrust. In theory you could achieve this with a different handling ofhttps , but lately I have come to think that the user expectation problems of such a solutionare insurmountable at this point; too many people just know what httpsin URLs means for its meaning to change (in a subtle way).

(My personal feeling is that it is pointless and even undesirable to gothe other way

Suppose that you have what I will call a 'directive style' configurationfile, where it looks something like (say):

fileserver fs1exportto hostsa:hostsbfilesys /h/10 fs1/d100filesys /h/11 fs1/d110

Further, suppose that you want to do things with this configuration filein a Bourne shell script, which requires parsing it to extract all of theinformation that you're interested in.

Normally this would be a pain

The idea of a dump program itself goes back to V6(Research) Unix, which introduced the first, rather basic dump program. At the time, Unix had neither tar nor cpio , so dump wasyour only option for backups. V7 Unix introduced tar , and I have theimpression that as a result dump fell out of favour for backups.

My impression is that dump really got popular in 4.x BSD. WhenBerkeley revised the filesystem format to create FFS (the FastFileSystem), with