New project but iso is too big

Ok, I'm back with a simpler method for a KNOPPIX splitted in two.

Here's the new minirt: ftp://belyi.ac93.org/pub/KNOPPIX/minirt26-knxapp.gz
The linuxrc diff file is here: ftp://belyi.ac93.org/pub/KNOPPIX/linuxrc-knxapp.patch
And the source of a small helper I used: ftp://belyi.ac93.org/pub/KNOPPIX/knxtest.c

The way you create a new KNOPPIX image is simple: rebuild bootable ISO image without compressed KNOPPIX file and with the new minirt26.gz, append this KNOPPIX file to the image padded to 2K if necessary and this is the image you would burn to CD.

So, if you have current KNOPPIX in KNOPPIX-3.7.iso file, the procedure will be something like this:
# mount -o loop KNOPPIX-3.7.iso /mnt/src
# mkdir newimage
# rsync -a --exclude=KNOPPIX/KNOPPIX /mnt/src/ newimage
# cp minirt26-knxapp.gz newimage/boot/isolinux/minirt26.gz
# mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 -boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat -hide-rr-moved -o KNOPPIX-prefix.iso newimage
# cat KNOPPIX-prefix.iso /mnt/src/KNOPPIX/KNOPPIX > KNOPPIX-new.iso
# dd if=/dev/zero bs=1 count=`ls -l KNOPPIX-new.iso | awk '{pad=$5%2048; if(pad) pad=2048-pad; print pad;}'` >> KNOPPIX-new.iso

The last step is necessary only if your CD burning software complains about the image not aligned to 2K block.
I wasn't able to come up with a procedure simpler than that. :smile:

Hope you like it.
Cheers,
Igor

Belyi;

Pleased to hear fro you this day and surprised that the system is so simple!

Will give it a go and let yopu know how it performs.

Tried out Puppy Linux while you were away and found it intriguing.

Now I will get to work!!!

Belyi:

The procedure produced a bootable DVD+RW disc that has a slow install for KDE. Myconfig is correct, internet OK.

The procedure was modified a small amount to permit it to run. The download of minirt26 generated a file in /tmp/kde-root with a coded ID. I changed it with RENAME to the specified...minirt26-knxapp.gz.

Rather than move the file, I changed the cp command; thus

cp /tmp/kde-root/minirt26-knxapp.gz newimage/boot/isolinux/minirt26.gz

No problem with mkisofs nor the burn with K3b.

I assume that this procedure will allow a large install >2GB in the concatenate step if a compatible kernel related KNOPPIX/KNOPPIX file is sustituted for the file that exists during the previous steps in /mnt/src..... before the cat step is initiated.

I appreciate this very much and am certainly thankful for your able guidance through the process.

There seems to be a great deal of interest in this activity and it certainly came out simplified!!!

Please make any pertinent comments on my effort...

For those who still interested - I've updated the linuxrc variant allowing compressed image to be appended to the boot image of KNOPPIX to work with KNOPPIX 3.8:

Patch for linuxrc: ftp://belyi.ac93.org/pub/KNOPPIX/lin...8-knxapp.patch
New minirt.gz: ftp://belyi.ac93.org/pub/KNOPPIX/minirt-3.8.gz

The procedure is the same as previously with just one difference - you need to update minirt.gz since there's no minirt26.gz in KNOPPIX 3.8

Cheers,
Igor

Belyi;

Performed the split format on Knoppix3.8 Cebit successfully.

Many thanks for your able support.

Progress, but not complete with added apps.

Burned a DVD+RW with added apps but it hangs with X displayed on screen, and no KDE.

The iso is 792MB and was generated with the "split".iso method of Belyi.

The procedure I used to get the .iso generated was derived from a method posted by Sunil Thomas Thonikuzhiyilhttp://www.linuxgazette.com/issue87/sunil.html http://www.linuxgazette.com/issue87/sunil.html

It was done in Kde using Knoppix3.8 Cebit.

My system has 2GB RAM, about 50GB of HDD space in Linux and a 2GB swap partition.

The procedure:

1. # mount /dev/hda3 /mnt/hda3
2. # cp -Rp /KNOPPIX /mnt/hda3/ ###/KNOPPIX is in root EDIT: Rp was RP ..../mnt/hda3/ ,,,was /mnt/hda3
3. # chroot /mnt/hda3/KNOPPIX
4. # mount -t proc /proc proc
5. # cd /etc #### to verify or change the nameserver
6. # Joe resolv.conf ####edit nameserver with desired editor save and exit
7.# cd return
8. # ping yahoo.com ### verify correct internet access
9. # apt-get update
9. #apt-get install amarok geomview enlightenment cinepaint digikam festival kweather #### just enough for testing procedures
10.#umount /proc
11.Control D
12. # cd /mnt/hda3
13. # mkdir NEWCD
14. # cd return
15. # cp Knoppix3.8 CDROM to NEWCD #### may require changing permissions with chmod 777
16. # mv NEWCD KNOPPIX/KNOPPIX (subdirectory) to desktop ######Edit: original KNOPPIX/KNOPPIX removed from NEWCD.KNOPPIX remains
17. # mkisofs -R /mnt/hda3/KNOPPIX | create_compressed_fs - 65536 > /mnt/hda3/NEWCD/KNOPPIX/KNOPPIX....###Edit: adds larger /KNOPPIX file to NEWCD.


This procedure created a 792MB CD file.

I utilized the NEWCD file in my normal Linux OS to generate an iso for use in the Belyi procedure........

1. # mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 -boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat -hide-rr-moved -o KNOPPIX.iso /NEWCD
2. # mount -o loop KNOPPIX.iso(from above) /mnt/src ##### this provides the expanded "split" .iso for the Belyi concatenation step, providing
the /KNOPPIX/KNOPPIX file therein.

My attempt ended with a boot to X in center of screen, internet access in root/tty4 and no KDE.

Perhaps I need a change in xorgconfig?

Quote:

---

Originally Posted by lilsirecho

...The iso is 792MB and was generated with the "split".iso method of Belyi.

---

Can you give a link to this "Belyi method" that you write of? I'm not having much luck with a Google search.

The Belyi procedure is in this forum item a few posts back. And even further back for the Knoppix 3.7 details.

It involves changing minirt.gz in the boot prefix.iso and utilizing a linear map procedure for the KNOPPIX/KNOPPIX file as the second of the "split".iso.

There are several posts by Belyi, the latest covers Knoppix3.8Cebit and the previous case he presented included a minirt26.gz for Knoppix3.7 Either of the two has produced a bootable "split" format.

My recent effort was to change the size of the Knoppix3.8Cebit to test the effect on the "split" performance. It is tantamount to a re-master but includes a "split" .iso as well.

It has the potential of producing a fully utilized DVD disc at 4.4GB...enuff to choke on!!!! It might take a month of eight hour days to "find" compatible apps which total ~9GB uncompressed!!!!

I ran seven apps in Unionfs with the 3.8Knoppix CD to ensure they were compatible before proceeding with my effort.

Perhaps they messed up my display parameters to cause the loss of any useable display. Mouse and keybd (usb) ok and ping OK. Just a big X, moveable!!!

Re-generated the remaster with the wiki mkisofs routine.....mkisofs -R -U -V etc.......

Now the new "split" .iso burn boots to...LINUX IN USE but an x error message says ...couldn't start kde init.....

Do I need a new mkisofs routine for Knoppix3.8 kernel 2.6.11?

Perhaps a fix is available?

I agree that "Belyi method" sounds confusing. For example, calling it knxapp gives much better result in google.

Lilsirecho, according to your description of the problem - the boot itself works fine but the startup of programs got mixed up.

According to what I saw in KNOPPIX, the startup files living in /etc/rc?.d directories are hand crafted and when there's a new one got added by upgrade or installation of an application it results in great confusion. What I would recommend to do after the upgrade - remove all /etc/rc?.d directories and copy them again from the original copy of the KNOPPIX. This will probably prevent your new applications to be launched at the startup time (in case they require it) but at least it should bring you to the same state which the original KNOPPIX did. You can always start your new applications afterwards.

Hope it helps,
Igor

Belyi;

Your suspicions are probably right.

It is strange that the programs ran ok when downloaded from Debian in Unionfs but can't run after full install. A messed up rc directory would make sense.

It brings up a question. How can a remaster boot correctly if such a thing happens? I may have to change how I add programs...say, get permission to load!!!!!

I feel that apt-get install should take care of the details and it did with Unionfs, putting the program into kdemenu(s).

Since it does install to Kdemenu, the probability is that it also hits other kde elements as well.

The mechanics of performing the removal of /etc/rc.d and subsequent install of the original is a big exercise in dual mounts of 790 MB each.

This problem will erupt every time I load new programs as far as I can tell if it is the /etc/rc.d directory.

It is kdeinit that does not start so its related to the init 5 steps.

I think I need to retry. I can select some other programs in a retry but have to uninstall those I have already in file. Another exercise1

Thanks for your support......

IBelyi;
Reviewed the remaster setup many times, performed many iterations and concluded with essentially the same thing I ended up with the first time. Kde does not initiate.

I made an iso with 748MB of apps and burned the iso. It booted to kde and the new apps were present in the KDE menu.

I used the prefix.iso generated earlier from the Knoppix3.8 CEBit and entered this new .iso via /mnt/src after mount -o loop and performed the cat concatenation.

Perhaps I have a problem with XFree by utilizing an .iso produced at a later time or maybe a time-stamp mixup.

I made a big effort to give this a second trial and know that the .iso I generated with added apps runs correctly. It is burned to DVD+RW.

The concatenation does not permit KDE to initialize. I used one less app, dropping kweather.

Can't decide what to do next...

Possibly the html file contains a clue to the difficulty?

EDIT: Perhaps a language problem? Font? Time and date? Myconfig--persistent home language? Boot log?

Seems likely it is in the boot ...prefix.iso.

Md5 mismatch?

Speak softly..use braille.

When faced with difficulties in performing Knoppix/Linux procedures, it is often a case of making errors.

In this case wherein I attempted to add programs to Knoppix3.8Cebit edition, I made errors in applying the re-mastering which affected the outcome.

I cleaned out my files and re-performed the whole shebang.

Lo! and behold...it worked. KDE came up and had all the new programs in the menu. The total size of the .iso is 748MB which was burned to DVD+RW at speed 4.

I am indebted to Belyi for his knxapp.gz procedure(s) and his patient replies to my questions.

I have outlined the procedure I used in a previous post as regards the remastering. The re-mastered .iso generated by the added apps is entered into /mnt/src to enable the concatenation with the KNOPPIX-prefix.iso and thus generates a KNOPPIX-full.iso having the new apps.

This procedure permits the addition of ~3.7GB of apps to the DVD burn (if you have the HDD space and the time to do the loading!!!!) :lol:

I regret having made all the errors :oops:

Hope this post helps another user to add to the KNOPPIX3.7 or 3.8 (either or both). The mkisofs routines are correct for these releases.

Good luck to users trying this means to make a larger than CD KNOPPIX burn!!



Speak softly..use braille.

Operated the "split".iso with 748MB of apps in TORAM mode.

I had to utilize 3GB of RAM to enable the loading TORAM to occur. It required more than 2GB to respond to TORAM loading.

TORAM loaded in ~4min 35sec.

Operation was faster than normal and those programs tested ran well.

I look forward to the summer release of a KNOPPIX DVD.




Speak softly..use braille.

After many attempts to use Video files to enhance the size of the KNOPPIX/KNOPPIX file, I decided to reverse my approach.

I entered the Video into the "prefix" newimage file before running the mkisofs command.

I entered too much Video in the first trial and it generated a concatenated file too large for the DVD disc.

I cut back to 2.4GB of Video in the Video directory I added to the newimage/KNOPPIX file.

I then ran the mkisofs routine to generate KNOPPIX-prefix.iso.

Having already made the "suffix" .iso , I entered it into /mnt/src.... mount -o loop KNOPPIX-suffix.iso /mnt/src

I then ran cat KNOPPIX-prefix.iso /mnt/src/KNOPPIX/KNOPPIX > KNOPPIX-final.iso.

This .iso was burned to DVD+RW in k3b.

The resultant DVD booted in 3minutes 39 seconds to KONQEROR display in desktop.

The video files are found in the CDROM under KNOPPIX directory/VIDEO subdirectory. They can be copied to /Desktop to eliminate the access delay from CDROM. When played from Desktop they are in RAM.

The DVD disc is nearly fully burned, perhaps 3/16 inch of radius left on the disc which is not yet burned.

The DVD has cloop, uncompressed video, UNIONFS, and Klik.cmg all operable from a LiveDVD capable of full 4.4GB write space.

The test performed confirms that the DVD can be loaded to full capability using the "split.iso" method and if the files are compressed in /KNOPPIX/KNOPPIX will produce a LiveDVD with 9GB of applications.

I ran....df -h.... and received the following:

__________________Device Size Used Avail Use Mounted On________________________________________________ ______

root 3.4M 17K 3.4M 1% /
Devhdc 3.2G 3.2G 0 100% /CDROM
Devcloop 1.9G 1.9G 0 100% /KNOPPIX
ramdisk 1.6G 23M 1.6G 2% /ramdisk
UNIONFS 7.9G 5.5G 2.4G 71% /UNIONFS


This LiveDVD demonstrates the use of compressed and uncompressed files together with Klik.cmg capability on a single bootable media with capability exceeding 9GB when using all file systems provided.

While booted in Knoppix v3.8, I created two .iso's of the /KNOPPIX /knoppix file, each with a different name.

I had previously generated a Knoppix-prefix.iso with modified minirt.gz per previous posts in this thread which I would concatenate with these as follows;

First, I concatenated the two identical .iso files (content identical) into a third .iso which listed as 1.4GB (twice the single KNOPPIX file size). Call it KNOPPIX3.iso....

Secondly, I concatenated the KNOPPIX-prefix.iso with the KNOPPIX3.iso.. as below;

cat KNOPPIX-prefix.iso KNOPPIX3.iso > Knoppix-final.iso

I burned the Knoppix-final .iso. It reported 4.6MB properties(Yes, 4.6MB=prefix size). Burned to DVD+RW 4x media.

I booted the DVD and had to make entries to get X and KDE running as follows;

/etc/init.d/xsession start
root# exec startx

The system then booted to Kde. I had to make internet connection via the ..network card configuration but it had all the necessary static IP and nameserver data installed. Operation following the initiation of internet was normal.

Obviously, the reported 4.6MB in properties on the DVD is only that part of the DVD which is recognized by the normal filesize utility. The "mapped" KNOPPIX files are not reported. Obviously, they are present because the KDE desktop and apps are all present. Equally obvious is that both of the KNOPPIX files are not active, at least not to my knowledge...AFAIK.

It seems apparent that if the KNOPPIX3.iso were provided with 4.3GB of apps that the result would be a fully loaded DVD disc but that it would be represented in the properties as a 4.6MB DVD! This may or may not be true when the size of the KNOPPIX.iso exceeds 2GB.

Next step...make a new .iso with two more concatenated /KNOPPIX files!


Speak softly..use braille..

Sign in vets office: Back in ten minutes. SIT STAY!

FWIW, I added two additional segments of KNOPPIX/KNOPPIX to increase the burn to 2.797GB.

The resultant burn produced a DVD+RW with properties of 4.6MB but the DVD has burned 2.797GB on the surface of the media.

This is characteristic of a "mapped" burn. It doesn't show KNOPPIX/KNOPPIX file on the DVD. The mapping is established by the minirt.gz change to V3.8 in the prefix.iso as stated previously.

It would seem possible to cat together, as I have done, numerous segments totalling a full sized DVD and having a net content which is an actual single KNOPPIX/KNOPPIX file of large proportions.

This is accomplished with techniques described previously in this thread by "split"technique, loop technique and crypt techniques (device-mapper) which can be applied to a large uncompressed KNOPPIX/KNOPPIX file.

AFAIK it should work but I haven't a clue as to how to use crypt (no encryption but utilize it with "none").

I write this while booted on the DVD. It boots as quickly as a normal boot of Knoppix v3.8 but I would expect it to
be longer if the full DVD was filled with a single /KNOPPIX file. It now has four identical /KNOPPIX files.

I guess I just have to fool around with KNOPPIX and not get bored!!!!!

Maybe the other three files can be addressed with cheatcodes even to the point of booting other versions? Probably not due to the prefix.iso being involved.

I have to try adding to the mix, just for fun!!!

I reasoned that I should be able to modify the KNOPPIX.iso to allow a full 4.4GB of stored programs if I modified the procedure generating a prefix and a suffix .iso.

Thus; if I modify the suffix.iso by using the re-mastering procedure, I can load 2GB of program material into the suffix.iso and that is a compatible level of storage for a DVD+RW disc.

Then; the prefix .iso can be modified (the minirt.gz changed to the Belyi provided minirt.gz as one element of change), by adding either uncompressed files or CMG compressed files to the KNOPPIX directory prior to running it through mkisofs.

I performed the following in generating a prefix.iso with both compressed and uncompressed programs:

Copied the KNOPPIX/KNOPPIX file from the booted KNOPPIX v 3.8.2 per the remaster procedure.
cp -RP /KNOPPIX /mnt/hdb3/.... this is cloop decompressed into /mnt/hdb3...

Re-booted to my archlinux system to enable preparation of the prefix.iso. .
Created ..newimage..folder in /mnt/hdb3

Copied the contents of the KNOPPIX v 3.8 CD into the newimage folder..

Deleted the KNOPPIX/KNOPPIX file from newimage.

Deleted the minirt.gz file from newimage and replaced it with the minirt.gz file obtained from Belyi for the 3.8 KNOPPIX version.

Entered the uncompressed KNOPPIX in /mnt/hdb3 in the KNOPPIX directory of newimage. ( this is a file of about 1.7GB).

Created a folder in Desktop called CMG and entered several CMG compressed files into it.

Entered the CMG folder into the newimage KNOPPIX directory.

Ran the following mkisofs routine:


mkisofs -pad -l -r -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 -boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat -hide-rr-moved -o /mnt/hdb3/KNOPPIX-prefix.iso /mnt/hdb3/newimage...........NOTE; no -J

The two .iso files were then concatenated:



(The suffix .iso was re-mastered in an earlier step and I find it convenient to just run the /KNOPPIX file in the
concatenation) This file could be copied into /mnt/hdb3 as well.

Thus, I do: cat /mnt/hdb3/KNOPPIX-prefix.iso /mnt/hdb3/KNOPPIX > /mnt/hdb3/KNOPPIX-final.iso EDIT: Properties=2.6GB

( This procedure differs from the /mnt/src/KNOPPIX/KNOPPIX as provided in Belyi's listing).

The result in my case was burned with DVD+RW media in k3b and booted correctly to KDE desktop.

I obtained access to the cdrom via /home/devices and opened the device. KNOPPIX directory held the uncompressed KNOPPIX and CMG folders which responded to selection by the mouse. The cmg files performed correctly and many games were accessed in the KNOPPIX uncompressed files.

This experiment proves that this method could provide for full-size 4.4GB LiveDVD with either 2GB in the normal KNOPPIX file and 2.4GB in the prefix .iso or leave the KNOPPIX file alone and load 3.7GB in to the prefix.iso. EDIT; the KNOPPIX file is the KNOPPIX/KNOPPIX file.

The device mapper introduced by the minirt.gz modification of the prefix.iso introduces the peculiarity that the KNOPPIX/KNOPPIX file no longer is present in an examination of the DVD contents in the normal way.

It should be possible to use other compression schemes in the prefix.iso besides CMG.

I haven't tried cloop in the prefix. EDIT: it would likely limit the added files to 2GB in the prefix. Perhaps cloop will be modified for DVD version?

This method doe not require splitting the uncompressed.iso and running compression routines on the splitted files and then doing loop procedures and device mapping.
The minirt.gz provides the necessary divider to permit full DVD involvement and thus the method doesn't actually require re-mastering the KNOPPIX/KNOPPIX file, just modify the prefix.iso.

Placing apt-get install programs in the prefix.iso probably won't. The prefix needs compressed files similar to CMG for best use of the DVD storage space in a LIVEDVD.
EDIT: Be aware that the ID for the booted DVD will likely be.....devicemappercdromcdrom...as it is in my system.

EDIT" I cannot find UNIONFS in the uncompressed KNOPPIX file added to the prefix. I wonder how it is handled in a cloop copy routine?

Latest news indicates a release of KNOPPIX 4.0 on DVD, stating that 9GB of uncompressed data is provided.

This willl be a big, big.big KNOPPIX release!!!!

It might be that the cloop file is provided at twice 2GB...thus is set at 4GB. This would accomodate systems limited to 4GB FAT related setups.

Actual full sized DVD is 4.4GB.

Quote:

---

Originally Posted by lilsirecho

It might be that the cloop file is provided at twice 2GB...thus is set at 4GB. This would accomodate systems limited to 4GB FAT related setups.

---

No, the cloop at 4 gb would not help. An iso bigger than 4 gig will be a problem to burn for anyone with FAT partitions.

In the normal CD, the cloop file is set at 2GB which is approx 1.8GB of KNOPPIX/KNOPPIX file uncompressed. (700MB CD size).

If the cloop were doubled to 4GB, then twice 1.8GB is available for the normal system loadup.

If device mapper were then used, the same loading would apply to a second 4GB cloop file.

Another way to state it is provide four separate cloop files of 2GB and use device mapper to enable loading at 2GB per compressed file and have four files.

An observation concerning DVD capability.

Should the device mapper be utilized on the DVD, a concatenated set of five cloop compressed files would produce 9GB of programs while utilizing 4GB of DVD disc space.

Reasoning: each cloop file produces a 700MB CD which has 1.8GB of program data. Five such files of compressed cloop data would therefore be five times 1.8GB which is 9GB. Five compressed cloops of 700MB is 3.5GB, below the 4GB breakdown point.

Perhaps there is a hole in my reasoning?

As of 6pm PST this day, no report of KNOPPIX DVD 4.0 on OSNews.

Quote:

---

Originally Posted by lilsirecho

As of 6pm PST this day, no report of KNOPPIX DVD 4.0 on OSNews.

---

I should hope not. The last thing we need is people posting "Where is the ISO?". Then when they figure out that there is a bittorrent of it, they all jump on it & clog the torrent with leechers. Based on my past bittorrent downloads (this is VERY subjective & based on my broadband connection), A well seeded A 4GB ISO (about 1:1 ratio of seeds to leeches) takes about 2 days to download. A poorly seeded 4GB ISO (1:20 or even 1:50) takes just about a week. I would prefer that we first get the torrent well seeded & distributed around the world before the rest of the net finds it.

Spent over a day downloading KNOPPIX 4.0 DVD via bittorrent only to get an error message saying " you must be downloading two files". After another half hour of retry, received the following;
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/BitTorrent/RawServer.py", line 385, in _make_wrapped_call
function(*args)
File "/usr/lib/python2.4/site-packages/khashmir/krpc.py", line 63, in data_came_in
c.datagramReceived(datagram, addr)
File "/usr/lib/python2.4/site-packages/khashmir/krpc.py", line 154, in datagramReceived
df.callback({'rsp' : msg[RSP], '_krpc_sender': addr})
File "/usr/lib/python2.4/site-packages/khashmir/defer.py", line 32, in callback
self.doCallbacks([result], self.callbacks)
File "/usr/lib/python2.4/site-packages/khashmir/defer.py", line 43, in doCallbacks
result = cb(result, *args, **kwargs)
File "/usr/lib/python2.4/site-packages/khashmir/utkhashmir.py", line 45, in checkSender
d = knode.KNodeBase.checkSender(self, dict)
File "/usr/lib/python2.4/site-packages/khashmir/knode.py", line 31, in checkSender
self.table.insertNode(self, contacted=1)
File "/usr/lib/python2.4/site-packages/khashmir/khashmir.py", line 172, in insertNode
old = self.table.insertNode(n, contacted=contacted)
File "/usr/lib/python2.4/site-packages/khashmir/ktable.py", line 107, in insertNode
assert node.id != NULL_ID
AssertionError
Cannot appreciate the bittorrent error messages!!

Solved the bittorrent problem by downloading the version 4.1.2 of bittorrent.

Mirror in archlinux did not have the latest so had to change mirror to get the correct version.

Should finish download tomorrow am.

Finished download of DVD, burned, and booted. Had to boot lang=us with german keybd "shift 0" entry for "=".

The background for DVD 4.0 is a time lapse photo of auto lights at dusk or nightime perhaps on the autobahn. If taken at 120mph or more, maybe time-lapse isn't necessary!!!!

The operations seem slower than the CD versions of KNOPPIX I am accustomed to using.

I was unable to use "myconfig=scan" because the boot-up ended with a solid "X" and no KDE.***********

I assume I may have to generate a new config file for the DVD**********.

I would appreciate any comment on that issue.*****************

The KDE start-up was slow in comparison to the normal CD.

I was able to enter internet params and gain access.

I left the bittorrent upload open all night.

Lots and lots to look at on the DVD which neeeeeearly fills the disc!! Might take as long as a week to examine the available programs.!!

Screenshots have been posted in the forums.

Klaus reports he will announce the official release of both the cd and DVD versions when the CD version is prepped.

The unionfs is used in formatting the DVD version which utilizes an additional KNOPPIX/KNOPPIX file to provide the "maxi" compressed DVD.

Re-mastering shpould also be possible if each of the /KNOPPIX files are below 2GB since the arrangement "splits" the program complement into two 2GB files. Data included in the "normal" /KNOPPIX provides for the boot function and the other /KNOPPIX does not include the boot data.

The process is similar to the prefix/suffix which I have been studying (without the cloop capability required).

In all cases the Kernel (and probably the cloop) must be the same as the DVD.iso...2.6.11.....

One observation concerning th LIVE DVD 4.0 is that it is compatible with klik cmg system.

If one desires, OPERA is available in cmg format and can be installed via klik.

If it is installed, it can be executed far faster than the DVD included "firefox".

This characteristic should prevail for all cmg-related files.

I found that myconfig was not responding from my hdd. Re-installed myconf and now all is well.

Cusromized the DVD for english and auto start-up by editing isolinux.cfg and re-burn.

For unknown reason, the internet access of myconf does not execute in DVD 4.0.

The data is present when the card config is re-entered.

Any ideas?