User Feedback :: Getting used to frugal



Quote (malanrich @ May 23 2008,23:38)
Thanks for the responses, guys.

I'll slowly work through the details of the wiki and maybe pick up the book too. Meanwhile, I'm okay with feeling a little dopey.

dopiness #1: I don't think making system time persist at reboot will work since I'm not online when I boot. (But I'll check more into this).

dopiness #2: I think I've understood the wiki on "Saving Your Settings," but I still can't figure why the glinks options file gets overwritten at each boot. I've enabled the Grub boot entry that includes mydsl, restore, persistency, etc., and mydsl, restore, home, and opt directories are designated as hda3. Since the glink options file is in the home/dsl/.links directory (also ramdisk/home... and mnt/hda3/home...), I can't see why the glinks options file isn't preserved.  Also, adding the directory for that file to filetool.lst fails to prevent the options file from being overwritten.

I'm sure I'm missing something very simple. Not a huge problem, since dillo satisfies pretty much all my online needs (plaease keep dillo!).

I've never used glinks, and see there's a glinks.uci extention that Robert compiled in 2005 you might try. If there's a particular file that gets overwritten  when it installs, you can always save the file somewhere and copy it over during boot by adding the instruction to /opt/bootlocal.sh  (using the "cp" command).
Quote (jpeters @ May 24 2008,04:05)
I've never used glinks, and see there's a glinks.uci extention that Robert compiled in 2005 you might try. If there's a particular file that gets overwritten  when it installs, you can always save the file somewhere and copy it over during boot by adding the instruction to /opt/bootlocal.sh  (using the "cp" command).

It is indeed glinks.uci that I'm using.

So if I place a copy of the options file in my home directory, what exactly would be the syntax for this in /opt/bootlocal.sh (so that it would be copied into the right directory for launching glinks?). I noted above that the glinks options file appears in three different directories, and I'm assuming that the one in home/dsl/.links and the one in ramdisk/home/dsl/.links are just links to the persistent one in mnt/hda3/home/dsl/.links (right?). So I need to direct bootlocal.sh to look in mnt/hda3..., right?

Sorry to be such a noob about this. The comments here are great. It's not that I'm married to glinks but that I'm learning alot about the DSL file system. Thanks...
Quote (malanrich @ May 24 2008,05:53)
Quote (jpeters @ May 24 2008,04:05)
I've never used glinks, and see there's a glinks.uci extention that Robert compiled in 2005 you might try. If there's a particular file that gets overwritten  when it installs, you can always save the file somewhere and copy it over during boot by adding the instruction to /opt/bootlocal.sh  (using the "cp" command).

It is indeed glinks.uci that I'm using.

So if I place a copy of the options file in my home directory, what exactly would be the syntax for this in /opt/bootlocal.sh (so that it would be copied into the right directory for launching glinks?). I noted above that the glinks options file appears in three different directories, and I'm assuming that the one in home/dsl/.links and the one in ramdisk/home/dsl/.links are just links to the persistent one in mnt/hda3/home/dsl/.links (right?). So I need to direct bootlocal.sh to look in mnt/hda3..., right?

Sorry to be such a noob about this. The comments here are great. It's not that I'm married to glinks but that I'm learning alot about the DSL file system. Thanks...

I just tried it.  What's happening in that the files in /home/dsl/.links
are removed when glinks.uci uninstalls.  Copy the .links folder somewhere on your /mnt/hda3 disk, and then overwrite the one installed when glinks.uci loads (assuming you have it in your mydsl folder so it installs on bootup.)
So in /opt/bootlocal:

rm -R /home/dsl/.links
cp -R /mnt/hda3/.links  /home/dsl

edit:  Don't forget to back them up when you make a change!

note: For a grub install, /home/dsl is generally on the ramdisk, which then can be backed up (e.g., to /mnt/hda3).
Success! Thanks to jpeters for the tips on preserving the options file. I'm writing from glinks now, and all my configuration settings remain intact.

The only glitch is getting the mydsl menu to boot glinks from the right directory (I think). There's a glinks executable (glinks.app) in the mydsl directory. That, and the glinks entry in the mydsl menu, executes a glinks that seems to be without any configuration at all--just a glinks gui. But the glinks executable in the opts/glinks directory calls up the right one with all my settings. It's some kind of path problem that I'll figure out.

Meanwhile, I'm happy with what I've got working. Thanks for the help.
If you're using a persistent home partition (edit: or backing up) so your settings carry over, you can add your own menu entries to launch things as you see fit. For example, setting up glinks to open by itself, to open to the DSL Forums, or to whatever site(s) you want. That can be done in the standard DSL menu or you can set up a separate menu and bind it to either a keystroke, a mouse key, or both and then launch applications however you want.

(My .jwmrc bears no resemblence to the original.)
Next Page...
original here.