mkmydsl problem in dsl 3.2

Forum: DSL Tips and Tricks
Topic: mkmydsl problem in dsl 3.2
started by: antoni_NT

Posted by antoni_NT on Jan. 19 2007,15:49

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.

Posted by roberts on Jan. 19 2007,21:16

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

Posted by antoni_NT on Jan. 20 2007,02:44

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?

Posted by roberts on Jan. 20 2007,06:12

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?

Posted by antoni_NT on Jan. 20 2007,09:59

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.....

Posted by roberts on Jan. 20 2007,15:00

Quote

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.

This is where the issue is. As the program states you must have booted with an autoscanned mydsl directory or have specified it, with a mydsl=xyz. In other words the system must boot into a working system with all extension loaded at boot time.

If you manually load extensions from the extension browser, there is no way the script would know from where, possibly many, locations, your extensions were loaded.

The mkmydsl is a simple remaster not a full remaster. As such it does not remaster a post installed/configured system. However with a little creativity much is possible.

Posted by antoni_NT on Jan. 20 2007,17:52

Let me clear it, so in the boot prompt I have to enter:

Code Sample

mydsl=/dev/hdb1

Where /dev/hdb1 is the place where mydsl directory exist and contains all of mydsl apps.
Am I right?
Thank you Roberts.
May I give suggestion. It would be better and interesting if you allow user to review the source for the cd before mkmydsl make the iso, before knoppix became an image. So user can edit boot logo, boot message, fixing faulty mkmydsl script (line 159 ;) ).
Anyway thank you. Sorry for posting this at this section.

Posted by ^thehatsrule^ on Jan. 20 2007,18:33

Quote

May I give suggestion. It would be better and interesting if you allow user to review the source for the cd before mkmydsl make the iso, before knoppix became an image. So user can edit boot logo, boot message, fixing faulty mkmydsl script (line 159 ;) ).

That is not the intention of mkmydsl - see roberts' previous post (last line).

And < http://damnsmalllinux.org/wiki/index.php/Cheat_Codes >

Posted by antoni_NT on Jan. 21 2007,00:22

Sorry again. When I boot using" mydsl=hdb1" (where hdb1 is the place of mydsl directory) will the mydsl apps inside it appear in mydsl rightclick menu? or I have to install it? Just make sure. Because, infact, it was not automatically added, gnu-utils, dsl-dpkg, alsadebs, enigma.uci.
Mr. Roberts, I still have this problem.

Code Sample

Enter the worrking directory.(EXAMPLE: /mnt/iso/): /mnt/hdb9
Enter optional boot time options:
Copying DSL image for remastering... Done.
umount: /cdrom2: not mounted
Checking for myDSL apps... Creating mydsl iso... mkisofs: Uh oh, I cant find the boot catalog directory 'KNOPPIX'!
Done.
If you have booted 'toram' or otherwise have access to a cdwriter, then...
Do you wish to proceed to burning the CD ? (y/..) n

What should I do, my Live CD located on cdrom1. boot using "dsl alsa toram mydsl=hdb1 dma"

Posted by ^thehatsrule^ on Jan. 21 2007,02:11

When in the current mydsl directory, they are loaded upon boot (you can see it in the boot messages). I think if in .../optional they are in the menu.

Posted by roberts on Jan. 21 2007,02:46

missing boot catalog, cdrom1, toram.... Yikes! Such complexity.

You must have 2 or more cdrom drives?

If you boot your CD from other than the first cdrom and also use toram, then I cannot tell from where you originally booted. So lets simplify.

Try without toram, your boot catalog will then be easily located.
- or -
If you insist on using toram, then boot CD from first cdrom drive and not the second one. Then the script should be able to use the knoppix standard to find the boot catalog.

HTH

Posted by antoni_NT on Jan. 21 2007,06:08

The problem solved, I need to get it on /dev/cdrom. Well, otherwise, the mydsl dir in iso file is empty. I don't see any mydsl apps there. Can U explain this?
Perhaps this help your suggestion. All of mydsl apps that I want to load automatically during boot are gnu-utils, dsl-dpkg, alsadebs, alsa_drivers, located on /dev/hdb1/mydsl/.
I boot using

Code Sample

mydsl=hdb1.

It supposed to be appear at right click menu under "myDSL", aren't they? But it didn't happen. I give some mydsl extension at ../mydsl/optional/ dir, and they don't show up there. ??!

Posted by roberts on Jan. 21 2007,06:31

You shouldn't even attempt to use mkmydsl unless you can boot the standard CD with the proper boot options.

If you extensions are /dev/hdb1/mydsl then using mydsl=hdb1 is not correct. Specifying a location overrides autoscan. If you want to specify your location, then it would be mydsl=hdb1/mydsl

Using your boot option, mydsl=hdb1 would not even work booting the standard DSL let alone expecting the mkmydsl to find your extensions.

Gosh, it is really easy.

If you can boot from standard DSL with proper boot options and find that your extensions are loaded, then and only then will mkmydsl know where to find things.

If you don't know how to boot standard DSL CD and required boot options then mkmydsl will only be confusing, as shown by this thread.

The opening message of the program clearly states these requirements..

Posted by antoni_NT on Jan. 21 2007,11:02

I'm so sorry, but my english skill is poor.

I bet you really disturbed with my topic post.

Ok, everything is just fine. BUT... :cool:

I place firefox-2.0-gtk1.uci on mydsl dir and also enigma.uci But it won't show up here. Is there any special tricks? Later, I moved those extension on optional directory, but error msg shown, "Please mount media containing optional dir and try again", when I tried the other one, gtk2-0705.dsl, it's OK.

How to run a command when boot progress. So, in order to make ALSA works, I need to make gnu-utils, dsl-dpkg, and alsadebs, loaded in ordered sequence, so I rename it, 1_gnu_utils, 2_dsl-dpkg, so forth. It works, but I still need to run "modprobe snd-via82xx;....: after boot finished.

Addition, how can I see boot message before xvesa run, I need to see bunch of error happened when mydsl was being installed.

Posted by roberts on Jan. 21 2007,16:37

On a custom CD, using toram and having uci or unc at the same time is inconsistent. toram means you asking that the cd be umounted. If the cd is umounted then how could mounted type apps work when the very device is now unmounted.

If you use the toram option and the uci and unc are placed in mydsl/optional/ then you will have to manually mount the cd after boot in order for these apps to be mounted. That is what the mesage is telling you.

If you avoid using toram you reduce your complexity.

It is standard procedure to use /opt/bootlocal.sh for your other required boot up commands.

On a custom CD you can use a variation of your backup.tar.gz call it myconf.tar.gz in which you can place in the mydl/ dir and it will autoload just as an extension would. For example your modprobe in /opt/bootlocal.sh could be in this myconf.tar.gz.

Posted by antoni_NT on Jan. 22 2007,00:58

Thank you very much Roberts. How can I contribute my help to DSL instead of donating?
Oh ya, I see release of DSL 4, which in size is over 50 mb? why it could be, what make it that size?
Don't you have a complete book introduction to new DSL user? at least in PDF? or online web? It could be useful for some new users.
Anyway thank you very much, I like envane theme style, it's the only one that change my mind to move to DSL. I don't like GNOME and KDE. It's to huge.

Posted by spock on Jan. 22 2007,04:40

Pdf ?

< http://distro.ibiblio.org/pub....pdfdocs >

Book ?

< http://spidertools.com/dsl.php >