MyDSL issue (DSL 4.2.5)


Forum: HD Install
Topic: MyDSL issue (DSL 4.2.5)
started by: Gustav

Posted by Gustav on Mar. 24 2008,02:52
I'm running DSL 4.2.5 on an old laptop (HD install) and I added some apps such as amsn.dsl, gcc.dsl, gimp-1.2.dsl and more (all .dsl extension). They work normally but, while DSL is booting (just before the bootlocal.sh commands), the following appears:
cannot open /tmp/mydsl.installed/amsn.dsl: File doen't exist
cannot open /tmp/mydsl.installed/gimp-1.2.dsl: File doesn't exist
... and so on (with all the apps I added).
It's really annoying because it takes like 20 seconds
Anyone can help me with this issue?
The apps work fine, I think it's just a mydsl problem
Thanks

Posted by jpeters on Mar. 24 2008,03:22
Quote (Gustav @ Mar. 23 2008,21:52)
I'm running DSL 4.2.5 on an old laptop (HD install) and I added some apps such as amsn.dsl, gcc.dsl, gimp-1.2.dsl and more (all .dsl extension). They work normally but, while DSL is booting (just before the bootlocal.sh commands), the following appears:
cannot open /tmp/mydsl.installed/amsn.dsl: File doen't exist
cannot open /tmp/mydsl.installed/gimp-1.2.dsl: File doesn't exist
... and so on (with all the apps I added).
It's really annoying because it takes like 20 seconds
Anyone can help me with this issue?
The apps work fine, I think it's just a mydsl problem
Thanks

I've never used a HD install, where I assume extensions are permanently installed. The tmp folder is used for extensions that are not, such as with a frugal install, live CD, etc.  Perhaps that is why those files  don't exist??

Posted by Gustav on Mar. 24 2008,03:53
Yeah, but why is DSL trying to open them?
Never happened this with HD installs of DSL 3.4...

Posted by jpeters on Mar. 24 2008,04:26
Quote (Gustav @ Mar. 23 2008,22:53)
Yeah, but why is DSL trying to open them?
Never happened this with HD installs of DSL 3.4...

I think there was a change in using the tmp folder for extension menus, etc., with 4.x.  Just ignore error messages that don't apply to your setup.

Posted by lucky13 on Mar. 24 2008,10:55
The bootlocal.sh script is for frugal installs, not hard drive. Your settings and extensions are persistent in a hard drive installation. You can safely remove the dsl extensions because they've already been written to disk.
Posted by curaga on Mar. 24 2008,15:10
Lucky13, it's not because of that. It seems to be a bug in one of the bootscripts, not taking HD-install into account (as it can have extensions installed but deleted)
Posted by Gustav on Mar. 24 2008,15:34
Quote (curaga @ Mar. 24 2008,07:10)
Lucky13, it's not because of that. It seems to be a bug in one of the bootscripts, not taking HD-install into account (as it can have extensions installed but deleted)

I agree with that. I've been trying to find which bootsript is causing the problem in order to edit it... but no results so far...

Posted by lucky13 on Mar. 24 2008,16:30
Quote
Lucky13, it's not because of that. It seems to be a bug in one of the bootscripts, not taking HD-install into account (as it can have extensions installed but deleted)

All the more reason to stop supporting hard drive installs. I know DSL works fine like that, but I still think people who want "Debian-like" systems should use something designed for that whether it's Debian or something like DeLi which is less bloated. Between the xfs/jfs/hfs(+) issues I had with the hotplug script and this kind of thing, it only reinforces the point that DSL should be either nomadic or "normal" and not try to cover every base.

Posted by roberts on Mar. 24 2008,16:34
The directory that you are writing about /tmp/mydsl.installed is normally deleted upon shutdown called from exitcheck.sh.

Therefore if extensions were once used and then later deleted there should be no more references to /tmp/mydsl.installed.

With a frugal or live CD the entire /tmp is on ramdisk and so it is gone upon shutdown.

I would suggest to check that you are running the exit program.

Otherwise manually delete that temporary directory /tmp/mydsl.installed.

Posted by Gustav on Mar. 24 2008,16:55
Quote (roberts @ Mar. 24 2008,08:34)
The directory that you are writing about /tmp/mydsl.installed is normally deleted upon shutdown called from exitcheck.sh.

Therefore if extensions were once used and then later deleted there should be no more references to /tmp/mydsl.installed.

With a frugal or live CD the entire /tmp is on ramdisk and so it is gone upon shutdown.

I would suggest to check that you are running the exit program.

Otherwise manually delete that temporary directory /tmp/mydsl.installed.

/tmp/mydsl.installed doesn't exist and I always used the exit program

The problem is that when DSL is loading, some script is trying to open those /tmp/mydsl.installed/...

Posted by roberts on Mar. 24 2008,18:34
Caveat emptor, mydsl extensions were never designed for traditional hard drive installations.

Since yours is such, I am guessing that you have mydsl-load commands in /opt/bootlocal.sh?

If so, then add mkdir /tmp/mydsl.installed before any such mydsl-loads.

Posted by curaga on Mar. 24 2008,20:04
I have seen this behavior, and I believe this case is similar.
In my case I installed gnucash.tar.gz to a HD install, permanently, and deleted the extension. My bootlocal.sh was empty. And I also got that error on boot about /tmp/mydsl.installed.

I didn't look further, as I had more important matters in mind (ie getting Gnucash to work), and now I don't have that system anymore.

Posted by Gustav on Mar. 24 2008,21:05
Here's my bootlocal.sh:

Code Sample
#!/bin/bash
# put other system startup command here
/sbin/syslogd
modprobe sb
loadkeys la-latin1


I think nothing there causes the problem. The thing is that all the apps are already in the HD (I work with them normally) and when DSL is loading, it tries to reinstall them but some files are missing (which I never erased). I just wanna stop DSL doing that...

Posted by roberts on Mar. 24 2008,22:01
What do you have in /tmp ? Any mdsyl.menu or such?
Posted by Gustav on Mar. 24 2008,22:29
Quote
What do you have in /tmp ? Any mdsyl.menu or such?


yes: mysdsl.menu and mydsl

Posted by roberts on Mar. 24 2008,23:16
OK. I reluctantly did a traditional hard drive installtion and am able to see the issue.

Thanks for hanging in there with me. Now I can go and fix it for the next release.

I will post later if I can give you the mods needed in exitcheck.sh. Let me test further first.

Posted by roberts on Mar. 25 2008,00:26
OK. This seems to do the trick...

In /usr/local/bin/exitcheck.sh currently line 33 reads:

sudo rm -rf /tmp/mydsl.installed

Change this line with the following two lines:

sudo rm -rf /tmp/mydsl.installed/*
sudo rm -rf /tmp/mydsl.menu/*

Posted by Gustav on Mar. 25 2008,02:00
Done! Thanks roberts and everybody else for the help.

Quote
All the more reason to stop supporting hard drive installs. I know DSL works fine like that, but I still think people who want "Debian-like" systems should use something designed for that whether it's Debian or something like DeLi which is less bloated

I know DSL isn't intended for hard drive installs, but I've tried with many other distros and DSL works faster than the rest on my old laptop (I can surf fast on the net, chat and hear mp3s, build my own apps, etc.).

Posted by pcdoctor on April 18 2008,00:42
Thx!  My strange bootup problem has been fixed!
Posted by pcdoctor on April 19 2008,07:26
After applying these settings, I can't see the mydsl programs (abiword, gnumeric,etc).

I assume this option causes the mydsl programs on the menu to disappear.
sudo rm -rf /tmp/mydsl.menu/*

I can't see anything when clicking on mydsl extension tool apps, themes, etc.

I put the original line back and rebooted.  I thought that would fix the problem but it didn't.

I tried this:
sudo rm -rf /tmp/mydsl.installed/*
sudo rm -rf /tmp/mydsl.menu/*

and this:
sudo rm -rf /tmp/mydsl.installed

but I still dont see anything after selecting mydsl extension tool.
Of course I used to be able to select themes and apps from the mydsl extension tool.
I hope I'm explaining everything ok.  Thx for all your help as usual!
Hmm.  the mydsl extension tool apps are back.
I think it might have something to do with my Internet connection.
In order to see the apps in mydsl extension tool does your Internet connection have to be working?
I'm going to post another network/internet connection problem that I'm having in another section.  Thx.

Posted by lucky13 on April 19 2008,13:31
Quote
In order to see the apps in mydsl extension tool does your Internet connection have to be working?

Yes, unless you're running your own repository mirror locally and have set that as the URI to look for MyDSL extensions.

You can manually edit your menu (jwm=.jwmrc, fluxbox=~/.fluxbox/menu) for the apps you've installed even if you've deleted the things in /tmp/mydsl.menu.

Posted by Gustav on April 22 2008,15:37
Quote
You can manually edit your menu (jwm=.jwmrc, fluxbox=~/.fluxbox/menu) for the apps you've installed even if you've deleted the things in /tmp/mydsl.menu.

Yeah, I had to edit the menu. As the apps are installed in your HD, you don't need to use the MyDSL extension tool. The next release will fix this issue:
Quote
Change log for v4.3RC1
* Improved removal of mydsl extensions on traditional hard drive installations.

Posted by flos on Feb. 20 2009,08:20
Thanks to all who participated in this thread.
Your persistence is admirable. Because of that, I have mended my DSL HD install.
I have a Toshiba 300CDT laptop which fails to get as far as loading a CLI for other distributions (Ubuntu flavours, Mint, SuSE, etc.) so DSL installed to hard disc is the only way for me to keep this machine running.
Well done!
Phil Headford

Powered by Ikonboard 3.1.2a
Ikonboard © 2001 Jarvis Entertainment Group, Inc.