DSL Tips and Tricks :: mkmydsl problem in dsl 3.2

Hey, thanks for finishing DSL 3.2. In my opinion, it's the coolest OS I've ever tried. But I got some problem.
I always have to use ALSA to get my soundcard plays. So, I have to install gnu-utils.dsl, dsl-dpkg.dsl, and alsadebs.dsl + ALSA-Drivers-1.0.11.dsl. Plus, I like enigma.dsl. The bad news is I have to do this routine every time I want to play around with DSL. It's tiring, time consuming. So, I tried mkmydsl script.
I thougth it would be very easy. But, it didn't happen. When I tried it. It yielded:

Code Sample

Checking for myDSL apps... Creating myDSL iso... mkisofs: Uh oh, I can't find the boot catalog directory 'KNOPPIX'!
Done.
/usr/sbin/mkmydsl: line 183: unexpected EOF while looking for matching '"'
/usr/sbin/mkmydsl: line 185: syntax error: unexpected end of file

I want to ask anybody read this and please answer it:
1. What the hell happened with those error message?
2. After done, I checked it at emelFM, there is nothing.
3. I tried earlier version of DSL (DSL 3.2 RC2), mkmydsl (playing on root shell) works well and created iso files that I could burn and boot. But:
3.a. I've never seen my previously myDSL extension shown in right click popup menu under MyDSL section (above "Apps"), so I have to install enigma, etc again. Why is this happen?
4. Despiting all problem I experienced above, how can I have a remastered CD that contains installed myDSL extension (such as: gnu-utils, dsl-dpkg, alsadebs, alsa driver, enigma, netcat) exactly as the same as the one I have that I use as mkmydsl source?

Please need help, I like this distro, I use this as my small, fast, multifunction tool.

There is a typo in the script but it does not affect the creation of the iso image. It does affect the last prompts to ask if you want to burn the iso. The line is at about 155 where I typed ( when I ment a {

echo "$(WHITE}If you have booted ...

That opening ( should in fact be a {

echo "${WHITE}If you have booted...

You can copy the script from /usr/sbin/mkmydsl to your home dir and make this trivial mod and then run from there

$ sudo ./mkmydsl

Ok, I'll handle it, but why mydsl apps didn't show up when it finished booting?
So at the message appear when booting,

Code Sample

"Checking mydsl applications....Done"

But, the apps never shown?
Should I place it (mydsl apps) in the /optional directory? at the root of the cd directory? or where?
I can't find these helps here, your search section is confusing. When I found it, it contains expert explanation, I don't get it.

----addition--
I have made fixation in previous explanation by roberts. So it offered me wheter I want to burn it or not. Nice. Yet, I still have the problem like in my first post. at the box code. Where mkisofs can't find boot catalog directory "KNOPPIX".
---addition again---
Sorry, I have just read the mkmydsl script, at few first line I see

Code Sample

cpmydslapps(){
[ -d "$SOURCE"/mydsl ] || mkdir "$SOURCE"/mydsl

I don't know much about script programming, but I guess, the $SOURCE is a variable, and I can't find any line that prompt the user to enter mydsl source? Like

Code Sample

read TARGET

at line 076.
So, how to fix this?

I just ran the script with no problems.
I included one of each kind of extension.

xchat.uci
xv.dsl
xeyes.tar.gz
xpdf.unc

Worked fine.

As the opening banner states:

You must have a working mydsl system upon boot from DSL cd.

That is your extensions are already downloaded and reside on a persistent store.

You must have booted with either a sepecified mydsl=hda10/mydsl or an autoscanned mydsl dir

If you system boots with your extensions ready to use then the mkmydsl script should find everything needed. Without any user intervention.

Only specifying an empty directory large enough to hold the entire mydsl.iso image is required and should reside on on a Linux partition.

If you are aborting with it not finding KNOPPIX then please answer the following:

1. Describe what you are booting from?
2. Where are your extensions stored?
3. What is the contents of System Stats Boot tab?
4. What extensions are located from No. 2 above?

Sorry, bothering you.
1. I boot from Live CD (always)
2. I store myDSL apps on /dev/hdb1.
3. I'll check it later (I'm running on Windows now)
4. The extensions are, gnu-utils.dsl, dsl-dpkg.dsl, alsadebs.dsl, ALSA-Drivers-1.0.11.dsl, and enigma.uci

I boot DSL in these order:
1. At boot option prompt I entered:

Code Sample

dsl alsa toram dma

2. When boot finsihed, I install extensions (from answer no. 4) from myDSL extension browser (without root previledges) > Local files. Then I point to /dev/hdb1.
3. I configure ALSA by entering:

Code Sample

modprobe snd-via82xx;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss

4. I set up enigma also.
5. Set up volume using dmix.
6. Test sound using xmms.
7. Then mkmydsl begins. First I tried from right click menu, Apps>Tools>"... remaster cd" (I forgot it)
8. Failed. The xterm window closed so fast, I can't even see what cause it.
9. I tried xterm root shell. I typed "mkmydsl" (I mod it just right your suggestion in this topic)
10. Then in the "Enter working directory" I entered /dev/hdb9/ (this is Linux ext3 fs, it was used by Slackware 10.0, I reformatted it)
11. At "Enter optional boot time options:" I tried enter

Code Sample

toram alsa dma

. (At later try, I gave nothing)
12. mkmydsl script end up with above error. (my first post)

Code Sample

Also there was message before it, it said: umount: cdrom2 (not mounted)
I have two optical drives. one identified as cdrom the other one cdrom1, I never have cdrom2. Then I move my liveCD (original one) to cdrom1. I rerun the cript, the message never shown again. But above error persist.
13. I reboot, and run with DSL 3.2 Release Candidate 2. Using exactly the same procedure. I found no problem and burn the iso file to cd.
14. I never get myDSL apps ready to use. I have to reinstall it instead.
15. When I checked the content of the cd, I can't find such myDSL apps, anywhere. And the size is the same with the original.

Are these right? Where did I do wrong? Do I have to use "myDSL=/dev/hdb1" at boot prompt?
Sorry bothering you. But help me please.....

Next Page...
original here.