DSL v4.4.7

Forum: Site News
Topic: DSL v4.4.7
started by: roberts

Posted by roberts on Oct. 29 2008,02:34

DSL Version 4.4.7 is now posted.

dsl-4.4.7.iso
dsl-4.4.7-syslinux.iso
dsl-4.4.7-vmx.zip
dsl-4.4.7-embedded.zip
dsl-4.4.7-initrd.iso

This minor update consists of user requests.

* Added fluxbox dock app, mount.app. Dropped wmswallow. Moved fluxter into slit to better accomodate wm restarts.
* Added .sylpheed/sylpheedrc with associations for: firefox %s, editor %s, xmms %s, and xzgv %s
* Adjusted .jwmrc & .fluxbox/menu Swap file now calls swapfile.lua instead of the dialog version.
* Improved backup. Now tests success before final shutdown. Dropped /opt/powerdown.sh, moved backup call to filetool.sh in exitcheck.sh
* Added directory option to restore boot code. Once used, must always specify, will not autoscan down into directories.

Files that have changed and likely in your backup:
.jwmrc
.fluxbox/menu
.fluxbox.inc
.fluxbox/fluxter.bb
.sylpheed/sylpheedrc

Note: Use extreme caution if you update your .sylpheed/sylpheedrc
You may want to note only the differences in your file and the one in /etc/skel/

Note: Use extreme caution with the new backup/restore. Best to make a copy and move it for safe keeping. Manually remove/rename /opt/powerdown.sh, as it is no longer used in 4.4.7.

Note: I will leave 4.4.6 in the current directory until I hear from those who requested the new features in 4.4.7

Note: It is always best to test new features with boot code of: base norestore

Posted by andrewb on Oct. 29 2008,03:26

I don't have my DSL laptop to hand at the present time, but....

Will the acpi power button event be affected by the removal of powerdown.sh? IIRC powerdown.sh is called by the power-button event to carry out a shutdown of the system.

Posted by roberts on Oct. 29 2008,03:44

Are you talking about extensions? I don't have any acpi capable laptops to test.
I suppose you can add a call to powerdown.sh from exitcheck.sh if wanted/needed.

Posted by andrewb on Oct. 29 2008,03:52

I'll check when I get back to my laptop & post the results.

Posted by Juanito on Oct. 29 2008,05:06

I was thinking it was "exitcheck.sh shutdown" that was called by a power button event?

Posted by andrewb on Oct. 29 2008,23:49

Quote (Juanito @ Oct. 29 2008,15:06)

I was thinking it was "exitcheck.sh shutdown" that was called by a power button event?

You are correct!

Posted by RRRR on Oct. 31 2008,01:10

Followed the instructions in first post.

First issue: After making a backup with filetool.app a message window (named "Unnamed") pops up informing:
Invalide device: sdb2
However backup have been made to sdb2 and there don't seem to be any problems with the backup.tar.gz as far as I can see. So I don't understand this errormessage. This is an issue I didn't have in 4.4.6

Second issue: A bit more problematic. The newly (re)introduced mount.app just won't mount or umount any device or partition at all. It just launches a dialoge box containing messages like "Unable to mount the device at this time.." and soforth...
I can easily mount and umount the same devices with 'emelfm as root user'. I also had no problem with the previous mount tool...

Posted by roberts on Oct. 31 2008,03:23

You should not have to mount or umount as root user. Therein points to your issue. Perhaps you have an extension that overwrites /bin/mount.

Both mount.app and cli $ was tested base norestore and also with gnu-utils.dsl. There is no /bin/mount in gnu-utils.dsl. Having such would explain your issue. If you have /bin/mount in your gnu-utils.dsl then you need to refresh gnu-utils.dsl gnu-utils was updatet (mount) removed when mount command was updated to allow user mount/umount many versions ago.

Posted by roberts on Oct. 31 2008,03:30

Any error during backup will cause a popup message, including trying to backup an non-existant file. You might want check the contents of /tmp/backup_status before you actually shutdown.

Posted by ^thehatsrule^ on Oct. 31 2008,05:15

Quote (roberts @ Oct. 31 2008,03:30)

Any error during backup will cause a popup message, including trying to backup an non-existant file. You might want check the contents of /tmp/backup_status before you actually shutdown.

On errors, does it suggest that to the user? i.e. "There were errors. Please check /tmp/backup_status"

And/or perhaps having a button to launch something to view it might be convenient.

Posted by RRRR on Oct. 31 2008,17:46

Quote (roberts @ Oct. 31 2008,03:23)

Seems I have gnu-utils.unc in. I don't have a chance to check this now but I'll do a troughout test when I'll get the chance and report back...

Posted by stunix*com on Oct. 31 2008,19:28

firstly, it works, i just mounted the 4.4.7 cd under a running 4.4.5 system, created /hda1/4.4.7 and copied the KNOPPIX file to it. then added a new line to grub specifying knoppix_dir=hda1/4.4.7 and restore=hda1/4.4.7 and restarted the machine. i get 4.4.7 with its own fresh conf.

yes i get various errors telling me the device is invalid when i try to backup, and again on shutdown, but i have so far ignored them.
;)

<edit> oh, and happy 37th to me! thanks for the prezzie Robert.</edit>

Posted by roberts on Oct. 31 2008,21:59

Quote (RRRR @ Oct. 31 2008,14:46)

Quote (roberts @ Oct. 31 2008,03:23)

Seems I have gnu-utils.unc in. I don't have a chance to check this now but I'll do a troughout test when I'll get the chance and report back...

It was gnu-utils.unc. It had not been updated and contained an old mount command that was overwriting the correct one.

I have updated gnu-utils.unc, check .info to see 10/31 entry regarding such.

Posted by roberts on Oct. 31 2008,22:02

Quote (stunix*com @ Oct. 31 2008,16:28)

Hey Happy B-Day Stu!
What happens if no dots in dir name?
Can you provide more info. I would like to clean it up.

Posted by stunix*com on Oct. 31 2008,23:06

thamks. hik.?!
tried renaming to 447 and got the same responses im afraid.

i havnt "done" anything with it yet ie just a "hi.txt" file in the /home/dsl dir. but i must be honest, i like the new corner arangement with mount.app maybe we could add the old and best wmix to it.

<edit>
*torsmorc is missing the exec line for torsmo_ip so the pumped ip address does not show indicating network up.
</edit>

Posted by RRRR on Nov. 04 2008,00:41

Right! Updating gnu-utils fixed the mount issue.

The backup error message was simply that I've deleted /opt/powerdown.sh as per instructed in post 1, but forgot to remove it's entry in .filetool.lst ....

...so all is good...

I would also support a request to get volume control back in the corner arrangement...

Posted by jls legalize on Nov. 04 2008,08:54

The backup script does not work if there are empty lines in .filetool.lst and also if a file or dir listed in the file does not exist.

legalize cannabis, coke, eroin...

Posted by roberts on Nov. 04 2008,12:40

That is true and one should correct their filetool.lst
filetool.lst is not a script. No blank lines allowed.
One cannot also use # for comments.
filetool.lst is simply a list of files and directories that should be backed up.

So clean up your list and then backup will proceed cleanly.

You can always open a shell and run filetool.lst backup and watch as the files are displayed during backup and see the areas that might need cleanup.

Posted by jls legalize on Nov. 06 2008,09:31

the default filetool still contains powerdown.sh so the backup fails, and the message invalide device is not correct. the correct error messagew should be: check your filetool

legalize cannabis, coke, ero.

Posted by stunix*com on Nov. 06 2008,11:51

yup it was the powerdown.sh in my filetool, too. all good now.

i put
execi 10 cat /tmp/backup_status
in my .torsmorc but in retrospect it doesnt really help much.

as a suggestion, how about a "test backup" option rather than having the "shutdown leap of faith" ie just checking if the files are accessable.

Posted by roberts on Nov. 06 2008,15:48

Agreed the default .filetool.lst should not have opt/powerdown.sh.
That and now the dslos.com/start expired domain, I will issue another maintenance release with this feedback under consideration.

Posted by stunix*com on Nov. 06 2008,17:00

i have some "on shutdown" commands in powerdown.sh, where should they go now?

<edit>
/usr/local/bin/exitcheck.sh
</edit>

Posted by roberts on Nov. 07 2008,05:23

exitcheck.sh either before or after the backup as required.