'BaDge' ( baj7d@virginia.edu ) wrote: Being a self-taught UNIX buff, and long-time DOS hacker, I was thrilled to see a link to an XTREE clone for UNIX, called Ytree. I normally use 'umenu', a popular shell for UNIX, and 'dired' a common frontend for fileops on my UNIX shell acct. I've also hacked together a cron script or two to gather UseNet articles, but that's about it. So it was with a little trepidation that I ftp'd the ytree archive ytree-1.61.tar.gz, and set about to unpack it and compile it. As most know, UNIX programs are distributed. as uncompiled C code, since there are different flavors of UNIX, each needing machine specific addins for the cursor functions, etc. I unpacked the code using 'gz', and then used tar: tar -xvf ytree-1.61.tar ...to unpack the archive. (there's a simpler way using zcat, but I can't recall the syntax). It unpacks to a dir called: ytree-1.61. Then I compiled the code, as per the instructions in the README file, and with a little tweaking, it compiled. Then I moved the compiled 'ytree' to my main dir. Note: the compile will try to copy the ytree program. to your machines main /bin dir, but you probably will get an error message since most don't have the permissions to do this. That's fine, just run it out of your acct main dir. Upon running it the first time, I almost killed the session. It takes 26 seconds to initialize! Why, I'm not sure, but it is probably logging the whole mounted disk. When ytree finally appears, it is breathtaking, with an almost exact emulation of the screen you see in DOS. The command options are different for UNIX, and appear as so: DIR Attribute Delete Filespec Group Log Mkdir Quit Commands Owner Rename Showall Tag Untag Execute ^FDirmode ...and then in the files window: FILE Attribute Copy Delete Edit File Group Hex Login Move Quit Commands Owner Pipe Rename Sort Tag Untag View Execute Pathcopy ^Filecopy I haven't tried them all, and the program assumes you have several support utils to do some of the fileview commands, so from here on, you're on your own! Try it! _____ BaDge baj7d@virginia.edu ======= Werner Bregulla, author of ytree replied: It has been criticized that loading time of ytree is rather long. In fact, it's not the loading of the program that takes that long, but rather the scanning of the entire tree! But even that can be configured: look at ~/.ytree , which contains the variable 'TREEDEPTH=2', it forces ytree to log to 2 directory branches on start. Decrease it's value to '0' and ytree is ready after just a second or so, but then the tree structure isn't logged yet, of course. Therefore you should set this value to such a degree, that all your files you normally work on, are loaded into memory at startup. It also has been mentioned, that a standard 'make' tries to install ytree to the main /bin dir. This could not be reproduced, for only a 'make install' will try to install (and the default install path is /usr/bin , rather than /bin, by the way ?!). _____ Werner Bregulla werner@frolix.han.de (translated from German)