I do intend to document this and make a tool to create a new adrive. It's just going to take some time - the whole concept is still under development.mikeslr wrote: When I unpacked the ISO, in addition to a Puppy's usual boot files, I also copied adrv_luki...sfs to the same folder. On boot up, Saluki reports that it found it. So I guess I'm using it. But frankly, I don't really know what it is, nor how best to make use of it. I recall, I think, some discussion that some apps would remain in --again I think-- Saluki's "core" which I assume (read that as ass u & me) is identical to puppy_luki_xxx.sfs, while others usually found in the puppy.sfs would be placed in "adrive", and that there was some way to move them from one to the other. Mavrothal's recent post indicated that he had booted without adrv. Did he not copy it from the ISO, or copy it other than to Saluki's folder, and if the later where?
I've been working with Puppies for about 5 years. I've read Saluki's entire thread, 'though not in one sitting. All of which is to suggest that if I'm confused about adrv, what would a newby make of it? and to suggest that a detailed explanation --perhaps in a txt file found in my-documents, with a menu entry-- might be appropriate.
I appreciate that the use of adrv is an innovation. But that is all the more reason to provide some sort of guide. As it evolves, the guide/instructions can be edited.
The basics are this:
If saluki doesn't find the adrive - you get only the core, which has no applications at all. You can then (once I fix the deps on some of the packages) install only apps you like from the ppm or other sources and then remaster.
Or you will be able to use the adrive builder to make your own personal adrive - the advantage to doing it this way is that you can upgrade the core easily when a new version comes out.