Fred, Toni; Here`s the new mk-menu files.
I added "find /usr/share/icons" to the mk-jwm.main exec. file.
It also has the new .jwmrc file to <Include> jwm.main and jwm.tail.
There is no jwm.head file any more, it is now .jwmrc.
The file /root/.jwm/.jwmrc is a back up copy, /root/.jwmrc is the active file.
Replace all the old files with the new ones, all the new files are changed.
Copy the files into the dirs they are in ( /opt/bin, /root/.jwm, /root ).

# I`ve noticed that jwm -reload does not always fix the menu, jwm -restart is needed.
I`m not sure exactly what the circumstances for this are, but I`m sure we`ll find out.

# Fred; Try this out, it should find audacity`s icon and show it on the menu.

I'm using the new DebianDog 01-v7.squashfs along with vmlinuz1 and initrd1.xz from DebianDog-PorteusDog-test.iso (which I had downloaded long time ago); all of these installed in /live. I'm using above menu.lst stanza except my files are in /dev/sdb1 so replacing above (hd0,0) with (hd1,0). Unfortunately, I am getting the following boot error message:

I see you added jwm.main in include tags. Not sure if this is the reason yet but something breaks the existing change menu-debian <-> menu-puppy
In /opt/bin menu-puppy and menu-debian change the /opt/bin/update-menus link to point to mk-jwm.menu or /usr/bin/update-menus and after that run /opt/bin/menu1 or menu2.
I can not think of better scheme to make both debian and mk-jwm menus working for user and root.
It starts to be like never ending circle of small changes that break more and more.
I don't know how IceWM uses icons but it has only this as IconPath in preferences file:

Converting desktop files from user when needed does not seems good approach to me.

Question to all: Way we try to replace well working and included in all debian wheezy packages debian menu method when not all desktop files follow the standards we try to include in mk-jwm.menu? I suggest we use Debian menu as default and fix mk-jwm.menu and make it default in some proper period of testing.

Terry, I might do something wrong, but desktop-convert gives this outputs. I make new desktop files by copy/paste from terminal to desktop file:

Hi, William.
You need not only initrd1.xz from DebianDog-PorteusDog .
You need to have /live/debian folder with all it content.
Also delete the two symlinks from /live/debian/base and create there new one /live/debian/base/01-v7.xzm pointing to /live/01-v7.squashfs
Or just move 01-v7.squashfs in /live/debian/base and rename it to 01-v7.xzm
Inside /live/debian folder you have this wheezy-i486.sgn file.

I'm working on this but it seems wheezy does not use fsck on boot. It has 6 months period check set. I'm not sure it will work the same way with downgraded initrd.img we use and with porteus-initrd file which is the second boot option.
To check the period fsck setup for every device use for sda1 for example:

Code:

tune2fs -l /dev/sda1

Creating file /forcefsck and reboot -F options does not work to make fsck on next boot.

Quote:

# Also, we need a default time sync utility, then no setup guis are needed.

What do you mean? Isn't it TimeZone setting menu entry enough? Every user will set up time zone once and it is done.

Quote:

## Toni; There are 2 Synaptics desktop files, one is for KDE, do we need it in our menu.?

No, but I keep the second one with no extension end it des not appear in the menu. Better to keep it this way in case someone need it after installing KDE on DebianDog

Quote:

## Added: So Toni found the "Set as Default" for the browsers.? We can use it...

yes, we can easy setup manual the default links in /usr/local/bin to point to different applications with Set-Default-apps. Personaly I do not like the idea every new installed browser auto-become default browser but we can do it as Fred suggested.

I've also now tried modifying menu.lst with changes=EXIT:/live/debian/

That seems to allow shutdown without saving changes (does in Portues-Wheezy anyway), but I haven't really checked that thoroughly. I did note however that unlike in Porteus-Wheezy I don't then get the nice splash choice to save or not. Would be good to include that and document DebianDog working with changes directory nicely for users. I've been using Porteus-Wheezy for some time simply because I love this changes directory method of persistence. I can manually just add or delete things in that changes directory and they have the desired effect on next boot. So I definitely plan to use DebianDog with that facility too rather than live-rw.

Of course, the changes directory method won't work on top of ntfs because of permisssion issues and symlinks not working there, but then live-rw is very tricky to make work on ntfs partition also, as I documented earlier. That is one of the better things in Puppy; Puppy save files work fine when stored on ntfs (on same or different partition to the other boot files), which is what I have habitually been doing for years (and never bothered making sure the ntfs area was defraged - still worked fine).

I'm not sure t searches subdirs, Terry. But it has only two paths in preferences and i don't think we had problems with icon showing after Fred found the fix for icewm-common. Maybe all icons are included in those two paths. Even if it searches subdirs I don't think we can easy include the same in Jwm.
Adding more PATH-s in .jwmrc looks better for me than copying and symlinking dirs and icons all the time.

DebianDog is pure Debian and it will use debian initrd by default. All other options that make DebianDog different from Debian are only options. You can also use linux-live initrd from here:
http://www.smokey01.com/saintless/Light-Wheezy/initrd-3.2.0-4-486-linux-live.xz
It is similar to porteus boot way.
Porteus boot way works well after adding small module with porteus changes. You can check it out in /live/debian/base
Save on EXIT works in DebianDog-PorteusDog-test.iso

mcewanw wrote:

So the question I have is: what is the difference with the way Puppy handles its save file to the way Debian handles live-rw?

I don't know and I never use NTFS. Having main squashfs module less than 100 Mb is small enough to use copy to ram and live-rw save file on NTFS partition. You have found one more different way to use it. It is enough for me. If someone else finds a way to use live-rw on NTFS without changing the debian boot way we will use it.
BTW I havent test this but as far as I remember Debian Wheezy docs says if you use persistence save file it works from NTFS partition. You can test it with not-downgraded initrd file if you like:
http://www.smokey01.com/saintless/Light-Wheezy/original-initrd.img/initrd1.img
You need to change persistent with peristence in kernel boot line and to use this save file:
http://www.smokey01.com/saintless/1Gb-persistence-or-live-rw.zip

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum