Auto loading Open Office
Forum: Other Help Topics
Topic: Auto loading Open Office
started by: mwdowns
Posted by mwdowns on Sep. 28 2006,00:48
Hello folks. 
I've been reading around here and the wiki, but I'm still a bit lost. I would like to have the Open Office extention to automatically load when DSL starts (rather than loading it manually using the myDSL application). I read that I need to put the extention into the myDSL folder. But, I have no idea where that folder is. I've looked in all the directories.
Also, just to be clear, I need to put the tar.bz file that I downloaded into the myDSL folder?
Thanks for your help.
Posted by ^thehatsrule^ on Sep. 28 2006,04:36
You could- place the command in /opt/bootlocal.sh
- use mydsl= bootcode
- place the file in / or /mydsl on the same partition as the DSL image.
Posted by mwdowns on Sep. 28 2006,06:20
| Quote (^thehatsrule^ @ Sep. 28 2006,00:36) |
| You could - place the command in /opt/bootlocal.sh - use mydsl= bootcode - place the file in / or /mydsl on the same partition as the DSL image. |
Still a bit confused. Sorry...slow learner here.
Is that a one-two-three "things to do" list you gave me? Meaning, I, one, open up the bootlocal.sh file; two, type in "mysdsl=bootcode" in said file; and three, place the tar.gz file in the / or /mydsl directory?
For number three in that sequence...I see no /mydsl directory. I see all the regular linux type directories (/KNOPPIX, /dev/, /opt, etc.), but no /mydsl directory. I did a frugal install of DSL, installing the knoppix image on hda1, and using hda3 as a persistant /home and /opt. Which directory in the list of directories when I open up Emelfm is the knoppix image in?
Sorry for being an idiot.
Posted by ^thehatsrule^ on Sep. 28 2006,15:20
Ah sorry, please insert an "either/or" wherever you please :PIt's just a choice of what you could use.
1. bootlocal.sh is a startup script, place your mydsl-load command there.
2. Bootcodes / Cheatcodes are entered upon boot. The mydsl= one just changes where (#3) below searches.
3. So your image is on hda1, so you can place it there on [hda1]/ or create [hda1]/mydsl (this is only used for newer DSL versions)
All of this is pretty much fairly documented somewhere - check the wiki, etc. for further readings.
Posted by mwdowns on Oct. 02 2006,06:20
Thanks for the clarification, ^thehatsrule^.I think I'm going to go with option 3.
However, when I try to make a file using CLI, I get a permission denied error. How do I sudo or su in DSL. I don't remember setting a root password or anything.
Posted by ^thehatsrule^ on Oct. 02 2006,13:48
There is no root password by default, and the dsl user is listed as a valid root sudoer.for just executing 1 command: sudo <command>
for a root terminal: "sudo su" or use just click the menu entry
Posted by mwdowns on Oct. 04 2006,05:50
OK. Got to the root terminal, but when I tried to create a myDSL folder on the / directory it doesn't show up after rebooting. It's there after I run the command mkdir myDSL and then ls. But if I reboot the myDSL directory disappears.Also, I tried doing option 1, and put mydsl=hda3/opt in the bootlocal.sh file (that is where the openoffice.tar.gz file is), but it doesn't work either. OpenOffice is not loaded during bootup.
What am I doing wrong?
Posted by ^thehatsrule^ on Oct. 04 2006,15:15
"[hda1]/ or create [hda1]/mydsl" <-- note that I indicated the mounted hda1 partition, not the / directory which is mounted on the ramdisk, which data is lost after each subsequest reboot. If /cdrom is mounted as rw (i.e. you booted with the "frugal" bootcode), you can use /cdrom/ or /cdrom/mydsl/In my earlier post, I thought I said those steps were a list of choices... the mydsl= bootcode has to be used by your bootloader. bootlocal.sh is for shell commands you want to run on startup.
If you require further reading, please see the wiki.
Posted by mwdowns on Oct. 05 2006,04:29
Hey ^thehatsrule^.I think I understand what you mean. What kind of shell script should I put in the bootlocal.sh?
Failing that, what exactly is the easiest way to get what I want done done?
The wiki is vague and doesn't offer much help. I've been looking at the page < for loading extentions at boot >, but it is short on specific examples. It talks about the mythical mydsl directory, but doesn't exactly say where it is or where exactly to put one. It gives you a boot code to use, but then points you to a page that is also vague on what exactly you're supposed to do if you have a frugal install (it does a good job explaining what to do if you have an hd install).
Basically I'm just lost. I have this extension. I want it to load during boot time. That's it. I can't figure out what I'm supposed to do.
Posted by ^thehatsrule^ on Oct. 06 2006,20:18
bootlocal.sh: add in your mydsl-load command here. i.e.| Code Sample |
| mydsl-load /path/to/my/extension.tar.gz |
The mydsl= bootcode is customizable so that you can place it _wherever_ you want. Of course you can make your own directory. The example in that wiki page still applies...
| Quote |
| For example, you can put your extensions in a directory called /mnt/hda1/home/dsl/mydsl and use the boot option mydsl=hda1/home/dsl/mydsl. |
Of course the easiest way to use the mydsl autoloading in your case would be for you to place the extensions just in the root of hda1 (see option 3). Using /cdrom or /mnt/hda1 or /cdrom/hda1/mydsl or /mnt/hda1/mydsl should allow you to place your file there. This way you don't have to use the bootcode at all!
Heh, it can get quite frustrating at times
Posted by mwdowns on Oct. 11 2006,00:56
The code sample you provided worked perfectly. Now Open Office loads at the start. Thanks for that. 
You should edit the wiki and put in that little bit of code as an example of what to do. I think it would help a lot.
Thanks again.
Posted by mikshaw on Oct. 11 2006,02:29
I was under the impression that the mydsl directory was implemented to remove the issue of people not knowing where to put mydsl extensions. Unfortunately I never quite understood why it would be any simpler for them unless the mydsl directory had already been provided in the iso, and automatically created when DSL is installed to harddrive.If a user doesn't understand what it means to save extensions to the top level of the DSL partition, he's also not going to understand what it means to create a directory in the top level of the DSL partition.
Posted by roberts on Oct. 11 2006,06:20
The mydsl directory was created so that no boot option would be required to autoload extensions. The idea is to be able to have a hands free boot from liveCD that would load up extensions and restore user backup. I could not premake a mydsl directory It can be on a hard drive partition, a pendrive, a CF, etc, etc. It does not have to be on the same level as, or even on the same partition as, the DSL (KNOPPIX) image. The last place I would recommend is under /home/dsl as that is the default for the backup/restore. Placing it there just ballons up the backup/restore. Which in turns slows down everything let alone using excess ramdisk. Extensions should always be separate from regular user files. Extensions being code and libaries are static. User files and configurations should be the only things within the backup/restore.
With so many combinations of options, including persistent home and opt. It is not always easy to give stock answers, either here or in the Wiki.
Many times, questions posted and answers to such are for a very particular set of combinations.
DSL, does not make decisions for you. With many choices comes complexitiy but also much flexibility..
There really is method to my madness.
Posted by mikshaw on Oct. 11 2006,10:06
I guess that would explain things nicely, thanks.Also I'm in full agreement about giving answers depending on combinations of options, to the point where I disagree with you =o)
Personally I have a mydsl directory in /home/dsl and it works well for me. However, this is used _without_ backup/restore and _with_ a persistent home so it does not suffer the resource waste that would accompany backing up extensions.