gLinks permanently

Forum: Apps
Topic: gLinks permanently
started by: toshiba

Posted by toshiba on Feb. 05 2007,20:48

I have installed 3.2 on a toshiba laptop with 32 MB RAM. Thus, many apps runs a bit uncomfortably, and a get the odd crash and such. The MyDSL system is great, and I stubled over the gLinks browser. It seems very suitable, as it's speedy, and crashes less often than dillo. Problem is, it being a .uci-app, I have to reinstall it upon every boot. Is there any way to install it permanently?

Posted by mikshaw on Feb. 05 2007,22:25

That depends on what type of installation you have.

If it's frugal, it won't stay installed, but you can have it automatically installed during boot by putting it in /cdrom/mydsl

If it's a debian-style harddrive install, mount the extension, copy the directory that was created in /opt, unmount the extension, and then rename the copied directory to the name of the original directory.

Posted by toshiba on Feb. 07 2007,12:04

Quote (mikshaw @ Feb. 05 2007,17:25)

If it's a debian-style harddrive install, mount the extension, copy the directory that was created in /opt, unmount the extension, and then rename the copied directory to the name of the original directory.

Thanks for the tip, but I can't actually get this to work. I tried to copy the glinks directory from /opt, unmount glinks with the uci-tool, and paste the glinks-directory back in. Trouble is, glinks disappears from the myDSL-menu, and I can't start the app from terminal either (typing "glinks"/"glink"). Any thoughts?

Posted by mikshaw on Feb. 07 2007,12:35

The icon/menu items are automatically removed when you unmount a uci extension. They can be found in the user.tar.gz archive in the /opt/glinks directory.
The icon files (the image and *.lnk file) go to /home/dsl/.xtdesktop, and the menu item must be added manually to /home/dsl/.fluxbox/menu
Do not reinstall the uci after replacing the icon files or you'll lose these files again. The menu item should remain as long as it's not put in /home/dsl/.fluxbox/mydsl.menu

You cannot currently start the application with a "glinks" command because the directory containing the executable is not part of your PATH variable. The simplest way to fix this in a traditional harddrive install is to symlink the glinks executable into /usr/local/bin:

Code Sample

sudo ln -s /opt/glinks/bin/glinks /usr/local/bin/

That assumes the file is /opt/glinks/bin/glinks, of course. I don't know if this is correct.

Posted by toshiba on Feb. 08 2007,16:45

Thanks, mikshaw. I haven't quite been able to crack this yet, but I'll keep tryin' for a bit.

Posted by mikshaw on Feb. 08 2007,18:49

Where are you having trouble, with the icon or the command?
Is the glinks directory in /opt at least staying put now?

An alternative to the symlink is an alias, which works in a frugal/liveCD system as well:

Code Sample

alias glinks='/opt/glinks/bin/glinks'

Put that in /home/dsl/.bash_profile and it should apply the next time you login.

Posted by toshiba on Feb. 10 2007,13:28

Let me summarize what I do:

1. I pick glinks.uci from the myDSL menu, and download it to /opt
2. glinks now is added to the fluxbox menu, and runs happily.

So, if I have understood you correctly, I'm should now:
1. copy the glinks-directory
2. Unmount the glinks.uci, usin the uci-tool in the fluxbox-menu.
3. Paste the glinks-directory back into /opt
4. Type the following in the terminal window:
sudo ln -s /opt/glinks/bin/glinks /usr/local/bin/[CODE]

So this is what I have done. When I try to start glinks from bash, though, it just says "command unknown".

Posted by ^thehatsrule^ on Feb. 10 2007,16:45

Is it actually there? Try

Code Sample

ls /opt/glinks/bin/glinks

Is there any output?

A direct way to find what's being used could be...

Code Sample

cat ~/.fluxbox/menu | grep -i glinks