Firefox plugins

Forum: DSL Ideas and Suggestions
Topic: Firefox plugins
started by: softgun

Posted by softgun on Jan. 11 2005,17:46

HI,

Firefox plugins are useful. The flash plugin is essential. While we can download the plugin into DSL Live CD each time. isn't there an easier way?

I made the .firefox_plugins directory with the flash plugins, put it ito the options directory. When I start booting from the CD, I rename the /ramdisk/opt/ .firefox_plugins and copy the .firefox_plugins directory I made to the /ramdisk/opt directory. Restat fluxbox and now flah pages are seen through firefox.

THis is tedious. Can this be automated to boot at bootup from the live CD without remastering/ISO hacking?

Thanks for yout suggestions

Posted by SaidinUnleashed on Jan. 11 2005,19:30

You can for your personal use, but I don't think it can be included in the distro.

Liscensing issues.

That's why we had to take flash out of the firefox extension, back at 0.8.x.

-J.P.

Posted by dvazquez on Jan. 11 2005,20:35

Maybe a .dsl ?

Posted by ke4nt1 on Jan. 11 2005,22:57

Nope.. no .dsl

Macromedia does not allow DSL, or any other entity,
to 'freely' distribute their ware.

That is why we have the link to 'get flash'

Once you have downloaded it the first time,
you can add the opt/.firefox_plugins directory to your
home/dsl/filetool.lst file, and run a backup.
Then your backup will save the plugin,
and reinstall it on your next bootup automatically.

73
ke4nt

Posted by softgun on Jan. 14 2005,13:14

"Once you have downloaded it the first time,
you can add the opt/.firefox_plugins directory to your
home/dsl/filetool.lst file, and run a backup.
Then your backup will save the plugin,
and reinstall it on your next bootup automatically."

Can I do this in the live CD?

Posted by mikshaw on Jan. 14 2005,15:22

That's what filetool.lst is for.
You just need to have a partition available somewhere on which to save the backup...it could be a harddrive, key, floppy, whatever, just as long as it's readable and writeable.

Posted by softgun on Jan. 15 2005,12:50

Quote (mikshaw @ Jan. 14 2005,10:22)

I know. But what i want to do is to add this to the CD and burn. Since I can only write to the root and optional partitions, how can i do this? Can i put in a .firefox_plugins directory into the root partition on the CD and modify and save the filetool.list to look there on bootup?

Can i do this with my bookmarks? Then when I boot with my live CD I will have all the bookmarks i commonly use available to me. BTW the index.html file in 0.9.2 says that the bookmarks are saved in /home/dsl/.phoenix . There is no such directory. Where are the bookmrks stored?

If these can be done easily, like we can add .dsl .uci by just writing to the CD and have them available on bootup, we can use the live CD without the need to depend on any other device to store them.

The DSL boast is that you can have your own configured live CD without remastering, right?

I think if these few configurations can be added in this simple way, any newbie to linux can potentially create his own live CD with just a CD burner.

Don't you agree?

Posted by mikshaw on Jan. 15 2005,15:44

the backup.tar.gz file which is typically created during the backup process can be placed in the root of the CD. When you boot up it will automatically extract into the proper directories, as long as the archive was created with paths intact.

Anything in $HOME can be put in filetool.lst as well.
/home/dsl/.phoenix is a hidden directory (note the dot), so you may need to unhide hidden files in order to see it in a file manager.

Posted by roberts on Jan. 15 2005,16:30

Don't put "the" backup.tar.gz on the root of the cdrom, as the autosave/restore will then try to write to it.

I guess it has been forgotten, so, I will post it once again. You can rename the backup.tar.gz to something else, e.g., myconf.tar.gz.

You can slim the contents down to whatever you like, or add more, it is not truly a backup but your personalized configurations, bookmarks, printer setup, mail setup, ppp setup, etc. Then use the backup featrure for those files that are changing between boots. It is up to you.

Then using mkmydsl script, you can make your custom DSL, with the features that you like, no remastering required. If your machine has a burner and DSL boots, then it is very easy.

For example, after I am finished with a release, I run mkmydsl and place myconf.tar.gz and the "toram" option to make my daily use mydsl.iso
You can also add as many extensions and optionals depending on the size of your cdrom or dvd, or specialized use.

DSL was desinged to be highly configurable.
In fact the mydsl system and mkmydsl which were released back in april 04 were from the beginning designed to make custom myDSL cd.
The loading extensions on demand were implemented a month later.

Posted by mikshaw on Jan. 15 2005,19:19

Quote

Don't put "the" backup.tar.gz on the root of the cdrom, as the autosave/restore will then try to write to it.

oh yeah...I forgot about that. I disabled the auto backup thingy in powerdown.sh so I can create by backups manually.

Posted by cbagger01 on Jan. 15 2005,22:10

echo "/opt/.firefox_plugins/" > flashlist.txt
tar -zcvf flash_plugin.tar.gz -T flashlist.txt

Include flash_plugin.tar.gz inside your livecd

Posted by softgun on Jan. 16 2005,11:39

Quote (roberts @ Jan. 15 2005,11:30)

Wow!

And I thought this was not possible! To me this was the only thing that prevented dsl from becoming the perfect live software system. You may have realised that i want to make a customised live Cd which i can use without depending on a usb stick r harddrive to bring up my config everytime!

I think you realise what this means. A complete newbie can, just download the dsl iso, burn to a CDRW or CDR with multisession/keep open fashion, add their plugins, make their keybindings, and then.....

backup these configurations as a tar.gz file, rename it as myconfig.tar.gz and put it in the root directory and after adding stuff from the rrepository and creating some more directories in the root for music/mpegs/presentations/pics, fill these with their favorites and burn his custom CD? (DO I have to edit filetoool.lst to say that my backup restore is myconfig.tar.gz?)

Is that it?

Shouldn't this go into the dsl documentation project? It is simply wonderful! How can this not be one of the major parts of the documentation?

Indeed, if you can get me to understand this, i will do it and document it myself!

What about mkmydsl script? Isn't this done online? If the above works why is this necessary? What advantages does running this script give over just backup as above?

Posted by roberts on Jan. 16 2005,13:40

It is a shame that the original concept that I had has been forgotten. Yes, load and use on demand feature of the extensions is very cool. But my original idea was to allow the user to make custom variable sized iso images, thus the name mydsl. The mkmydsl script is probably one of the most overlooked scripts in DSL, yet it has been there since day one when I released the myDSL system and the six example extensions that I made to start this whole thing. Why is it not in the documentation is a very good question.

mkmydsl is NOT myDslMaker. mkmydsl is done locally. This has several advantages over a website version of the same thing including:
1. "Try before you burn" You can download extensions and try them out before you commit to makeing an iso and burning.
2. "Construction Set" by downloading in parts, you truly have a construction set method. This makes it easier for a slow modem users to be able to take advantage by not having to download a large single mydsl.iso
3. "Privacy" By makeing the iso locally, you are not "sending" private information to a website only to have to download the results back. This is where the myconf.tar.gz comes into play. This is your "personal" and "private" configuration including passwords, etc.
4. "No double down" You already have the base iso and have proved that it works on your system, so you don't have to download it again only this time MUCH bigger. Also, you already have your local "proven" collection of extensions
5. "The Sky 's the Limit" I know of one user, Ke4nt, who uses the mkmydsl script to make DVD sized mydsl.iso. Imagine having to download DVD sized images.

The myconf.tar.gz is for your configs that you will not be changing. Thus filetool list remains for backup.tar.gz. My myconf.tar.gz has firefox FLASH plugin, Sylpheed email settings, my network printer configs, and several PPP settings and providers. mkmydsl script also allows for the boot time options to be passed, so I use toram, but you could also set your keyboard, start various daemons, e.g., ssh, lpd, etc.

I made the script to work on the most minimal of systems, e.g., a machine that is capable of booting DSL toram and a working cdrom burner is optional. It does not need multi-session.

By answering a few simple questions you can have your mydsl.iso created and ready to burn. If you have a burner, you can continue the script to burn to cdrom.

When I write scripts for DSL, I try to write to maximize the amount of machine that will be able to use the script. The script does not require the latest "super blasto" computer. Although it will run from within X via xterms, I usually run it from runlevel 2. By simplying answering a couple questions. Your done!

This is how:
Lets say that you have downloaded and have a nice proven collection of extensions on your harddrive say hda3

Step 1: booting
boot: dsl 2 toram
Step 2: mounting your extensions library
# mount /mnt/hda3
Step 3: Start the script
# mkmydsl
Step 4: You will be prompted to enter the location of your extension library
Enter the directory to hold the image and modules: /mnt/hda3
Step 5: You will be prompted to enter the location to write the mydsl.iso
Enter the directory to hold the new iso:
Step 6: You can enter additional boot time options
Enter optional boot time options:
Step 7: Optional additional setup of extension library
You will be prompted to copy any "last minute" extensions. This step is not needed if the extension library is already setup with "root" and "optional". This step is useful if you have large ram and are using ramdisk directories, then you will need to copy over the extension library into the ramdisk. But normally the step is not nedded.
Step 8:Final approval
When you are ready to begin creating the ISO enter OK. (literally means capital OK
The script creates a mydsl.iso
Step 9: Optional buring step
You will be prompted to once again enter capitals OK to begin the burn. If you don't have a burner then press enter and your mydsl.iso is made. Entering OK you will be prompted to enter th burn speed and device numjber for the burner.
Thats it.

Like I say, I use the script after EVERY release to make "my" customized version for daily use.

Note: use the command
cdrecord --scanbus to learn the device number for your burner.

P.S. Note: NO WINDOWS REQUIRED!

Posted by softgun on Jan. 16 2005,15:08

A few questions

Posted by softgun on Jan. 16 2005,15:20

I agree wholeheartedly. This ability is the coolest thing about DSL. It must be in the documentation and even in the index file that pops up.

I have jottted a few questions for clarification.

Before i run the script, do I need to backup and rename the file myconfig.tar.gz ?

Then I boot with toram option and run the script and add the extensions. Does it take care of the above config file as well or do I have to copy this to the root directory myself?

Posted by roberts on Jan. 16 2005,15:43

It is in the popup page "Getting Started". I wrote that page. But it is just mentioned there. Near the bottom.

The best way to test beforehand is to use and understand the boot time option of mydsl=hda3

So, test first with the standard liveCD and a partition, say hda3, and boot with:
dsl mydsl=hda3

Once everything is working and you want a custom CD then use mkmydsl script.

So, to answer your question, you have to have already made your myconf.tar.gz and it need to be located in the "root" of hda3.

For example lets say /mnt/hda3 would look like this

myconf.tar.gz
flash.tar.gz
xchat.dsl
optional/
ruby.dsl
php.tar.gz
gcc1.dsl
gnu-utils.dsl

Then using the regular liveCD boot time mydsl=hda3 you test everything
upon bootup flash, your configs, and xchat are autoloaded, and the others are shown on the menu as optionals.

Finally, after everything is working, then run mkmydsl and specify /mnt/hda3 as the target "master" directory and specify the target iso directory. Done!

Posted by softgun on Jan. 16 2005,17:45

Did this.
It is excellent for adding extensions, but the configuration saving thing did not work.

the flash.tar.gz is no longer available in the repository.

This is what i did

I added the flash.plugin online/
I copied the bookmarks.html file from my old firefox to the /home/dsl/.mozilla/firefox/xxxdefault directory on the liveCD and it worked, but obviously it did not work with the backup. On reboot no flash and no bookmarks :-(

How can i get the flash plugin and the bookmarks in (without having to add all the bookmarks manually) on booting?

Posted by roberts on Jan. 16 2005,19:07

You make the flash.tar.gz and myconf.tar.gz as your own personal private extensions. See cbagger's post for suggestion. You use the tar command to make it.

There is no flash.tar.gz in the repository because of license.

But after you download your own copy, then use tar command to make your own "private" dsl extension.

Believe me it works.

It is just alot to learn at first. But is it worth it? You betcha!

Posted by ke4nt1 on Jan. 16 2005,20:49

Let me jump in here and BRAG about the mkmydsl, since I'm its biggest fan !!

After 9 months of working with every extension in the repository,
extension building is a natural part of my everyday DSL activities.
In my daily use DVD's, I have my "myfonts.dsl" , "allthemes.tar.gz",
"myprinter.dsl" , "mywine.dsl" , "plugins.tar.gz" ,
( why limit to only flash, stick libjavaplugin and mplayerplugin in there too )
and several others. you get the idea. These are all homebrew.
( I think extension building could be a major topic all by itself,
as I am seeing more and more examples of unique and creative ways/uses. )

Following cbagger01's earlier example is a very easy way to begin making your
custom extension. Further tailoring of the list.txt file is also possible to
whittle down even more stuff to keep your extensions "thin" and responsive.

I have made custom bootable DVD-R's for my children, mother-in-law, friends,
and co-workers.. Making custom isos is great for showing-off the latest
and greatest linux software to friends (linux and non-linux users alike) .
There is no installing, no setup, just click-n-run, in the true mydsl tradition.
I frequently install a homebrew style with a theme I know they would enjoy.
( favorite band, simpsons, religious, whatever the person likes. ) ,
along with some extensions that cater to their interests.
( music, games, office apps, or even the whole repository! )
With 4.4GB's, your not really limited sizewise.. although I have filled several!

Obviously, one must know a little info about the hardware inside
another persons system to do this successfully.
For those folks that I know who have somewhat beefier systems,
and NVidia video, Henk1955's XFree86.dsl contribution,
and the nvidia.dsl extension have, in combination with the mkmydsl system,
allowed me to make bootable, super gaming DVD's for my kids and others.
Read my blog contribs for more detail in the talk section of the DSL website.

With DVDR media falling in price, (I'm seeing under 40 cents for 4X AZO dye) ,
and the writers as well, DVD-R's will soon overtake CD media in popularity.
I feel that DSL, and the mkmydsl are ready-to-ride for DVD.
I feel it is now "well tested" , and completely successful.
I have made dozens, without issue..

I also vote for Robert to include more information about this feature
in future "Getting Started" introduction pages, in later DSL builds.
Including a simple example of making the flash.tar.gz would also be helpful.
( as shown above.. )

I feel there is still a need for a writable area for your backup.tar.gz file(s).
I use several, selecting a particular one at boottime, for experimenting
with changes to the filesystem. ( if it busts, just reboot with the earlier one )
It's also an easy way to work with changes to your system, and keeping up
with everchanging bookmarks, email, and game scores, etc.
But for the static stuff, mkmydsl is " the right stuff" . It's almost TOO good !

We DSL folks are SO spoiled.. tnx Robert.

73
ke4nt

Posted by ke4nt1 on Jan. 16 2005,20:51

bookmark

Posted by softgun on Jan. 17 2005,07:59

I agree with both of you. The availability and the way this script is used must be clearly and prominently displayed in both the index file popping up on the CD, the index page on the dsl site and in the documentation.

Instead of a flash.tar.gz i have made the firefox_plugins directory and my bookmarks.html file and copied them to the root fo the cd. Then I made a small script file and put it there too and burned it after putting a few programs from the repository - rox, skype, openoffice.uci. mplayer and mplayerplugin.
I made several directories and put in music, presentaions, web pages, pics etc and just burnt them all in :-)

Now i boot up to the usual dsl.
Then I open the file manager and in front of my chldren,friends, students, and click on flash_script (to run my script putting flash in), copy the bookmarks file to tha appopriate directory and then bsetbg -f path to a pic from a collection and magically it is all set to go.

BTW my script to copy the bookmarks.html file to the home/dsl/.mozilla/firefox/defauls.xxx fail because the xxx in defaults.xxx changes each and every time. putting in a default.* does not work :-(
Any way round this?

This may seem like too many steps to you, but in fct it is better this way as you get what you need when you need t and the basic dsl runs by defalut.

If I need open office to show a presentaion for example, I start it off!

I then tried the mkmydsl script with a cdrw and that is even better! However it does not solve the bookmarks saving thingy.

To think that I had to get to know this from the original author because it is played down so much is not funny.

It's unfair!

Was it meant to blush unseen?

Posted by softgun on Jan. 17 2005,10:29

Quote (cbagger01 @ Jan. 15 2005,17:10)

echo "/opt/.firefox_plugins/" > flashlist.txt
tar -zcvf flash_plugin.tar.gz -T flashlist.txt

Include flash_plugin.tar.gz inside your livecd

Thanks chagger,

I will do that soon. For now i run a script to do this every time I start up. This way I am in total control and run the basic dsl, which i show everyone and then show what we can do :-)

I have told them that this can be automated......

I want everyone I know to use dsl and the "Top Secret" mkmydsl script ;-) - from roberts to create one customised for themselves.

Posted by softgun on Jan. 17 2005,10:29

Quote (cbagger01 @ Jan. 15 2005,17:10)

echo "/opt/.firefox_plugins/" > flashlist.txt
tar -zcvf flash_plugin.tar.gz -T flashlist.txt

Include flash_plugin.tar.gz inside your livecd

Thanks chagger,

Do I do this as root or as dsl user?

Posted by cbagger01 on Jan. 19 2005,17:58

You don't need to be root to do this, as long as you have write access to your current directory.

In other words, run this from /home/dsl and your flash_plugin.tar.gz file will be written to this directory. No "root" access is needed.

Posted by softgun on Jan. 23 2005,16:42

I did it successfully.
Thanks again!

Posted by Rapidweather on May 08 2005,14:08

Testing DSL 1.1:
The Menu -> Apps -> Net -> Get Flash Plugin script asks that we add opt/.firefox to our filetool.lst to save the flash program.
Should that be opt/.firefox_plugins
Anyway, it works, and I did add that to my filetool.lst.
I searched around and did not find another post on this subject, so I put it here.
Still amazed and delighted with the automatic backup/restore for DSL. Ease of use
for newbies will be way up near the top of all liveCD distros (If not at the top).
Key item here is also the button in Emelfm, to add something to your filetool.lst,
in addition to the scripts themselves where the backup file is obtained on bootup,
and written to on shutdown.