Results 1 to 1 of 1

Thread: What's UpDock?

  1. #1
    Senior Member registered user
    Join Date
    May 2006
    Columbia, Maryland USA

    What's UpDock?

    Here's an abbreviated tally of the cloops saved at /mnt-system/KNOPPIX/
    on my current Knoppix 7.7 CeBIT version LiveUSB:
    knoppix@Microknoppix:~$ ls -l -o -h /mnt-system/KNOPPIX | grep KN
    -rwxrwxrwx 1 root 4.0G Apr 14 06:30 KNOPPIX      The basic Knoppix 7 DVD 
    -rwxrwxrwx 1 root 171M Apr 14 06:30 KNOPPIX1     Recent 3d & backup programs
    -rwxrwxrwx 1 root 7.5M Apr 14 06:30 KNOPPIX2     Flashplugin-nonfree
    -rwxrwxrwx 1 root  76M Apr 14 06:31 KNOPPIX3     My own tweaks & additions
    /mnt-system/KNOPPIX/ is a folder or directory on a FAT32 filesystem
    which has a filesize limitation of just a little over 4 Gb. KNOPPIX, aka
    KNOPPIX0, uses virtually all of the 4 Gb capability of a cloop device
    on FAT32 to define most all of Knoppix 7 DVD's basic contents.

    KNOPPIX1 contents plus KNOPPIX0's plus some auxiliary files would produce
    a collection which would be slightly over the 4 Gb FAT32 filesize limit,
    hence KNOPPIX1 contents are given their own cloop.
    Since there are, at present, eight unique cloop device assignments, there
    may be additional KNOPPIX[n]s defined, each having a 4 Gb capacity.

    I postulate that KNOPPIX2 is Klaus K's way of providing the CeBIT Knoppix
    version with proprietary flash material on the 7.7 DVD using LinuxPro
    Magazine's authority to distribute.

    KNOPPIX3 is my own current use of Knoppix cloops to make a read-only,
    compact representation of my own tweaks & additions initially to a
    read-write, not-compact, reiserfs persistence file, KNOPPIX-DATA.
    I use a small bash program to do this.
    See the following, where MakeOverlay is what I now call save.overlay:

    With the advent of overlayfs, and especially using a 4.0-or-later kernel
    there are opportunities to further aggregate & compact Knoppix cloop material.
    It seems plausible that another small bash program might be similarly
    useful to further agregate the initial contents K'1, K'2 and K'3 into
    a new but larger but still-much-less-than-4 Gb re-defined K'1. The following
    two references lead me to believe this:
    See the answer to the cited question in...
    And, for additional expository material, see...

    Immediate project:
    I have in mind eventually defining a small bash program which I might call
    merge.overlays, using the cited material and some additional ideas in:
    Last edited by utu; 04-15-2016 at 08:41 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts