iB::Topic::mkmydsl problem in dsl 3.2

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » DSL Tips and Tricks » mkmydsl problem in dsl 3.2

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (4) </ 1 2 [3] 4 >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: mkmydsl problem in dsl 3.2

< Next Oldest | Next Newest >

roberts

Group: Members
Posts: 4983
Joined: Oct. 2003

Posted: 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

antoni_NT

Group: Members
Posts: 12
Joined: April 2006

Posted: 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. ??!

roberts

Group: Members
Posts: 4983
Joined: Oct. 2003

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

antoni_NT

Group: Members
Posts: 12
Joined: April 2006

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

roberts

Group: Members
Posts: 4983
Joined: Oct. 2003

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

16 replies since Jan. 19 2007,15:49

< Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (4) </ 1 2 [3] 4 >/

Damn Small Linux Board » Damn Small Linux » DSL Tips and Tricks » mkmydsl problem in dsl 3.2