Light-Debian-Core-Live-CD-Wheezy + Porteus-Wheezy

For talk and support relating specifically to Puppy derivatives
Message
Author
User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#1961 Post by fredx181 »

Hi Toni
Just a thought for extra option.
It needs apt-get update to be run before starting apt2sfs. Maybe running apt-get update at program start up as default?
Yes, good idea, I made a checkbox for it.
Also made it do some "zerosizing" to save some space.

I edited my post on previous page and new version uploaded there.

Fred

mcewanw
Posts: 3169
Joined: Thu 16 Aug 2007, 10:48
Contact:

#1962 Post by mcewanw »

saintless wrote: Unfortunately some package developers do not make menu files for debian menu system and have only desktop packages included. This is the future package management behaviour. This means debian packages outside debian wheezy repository may not have menu files included. Debian developers maybe will follow this method for the next stable debian or try to adapt current debian menu to use desktop files.
If we change the menu method it is better to use desktop files. This way we will have separate working replacement for debian menu system.
I absolutely agree with this last comment. Making menu from desktop files is the way to go. I would be surprised if Debian developers didn't in the future move to a menu based on desktop files also. In the meantime shouldn't be too difficult to make a few desktop files for any packages that didn't supply one by default. Terry's menu looking good.
github mcewanw

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#1963 Post by fredx181 »

Hi Toni, William
Here's IMO an important addition to DebianDog-Porteus:
It will give an option (in case boot parameter changes=EXIT:/) to save changes or not when shutdown/reboot from terminal or console instead of only when X is running.
It works also when pressing Ctrl+Alt+Del from some tty.
It gives a simple question on the console, but when you install the 'dialog' package, then there will be a nicer "dialog".
See below for: snapexit_0.1.1-1_i386.deb (remove dummy .tar extension)

Toni, I wanted to add this to the 021-apps-porteus.xzm module but AFAIK it isn't reliable because of changes in the shutdown order (changed symbolic links in e.g. /etc/rc6).
So the best thing I can think of is to include it in the main module.
I made sure it doesn't run when using the live-boot DebianDog version.

Fred
Attachments
snapexit_0.1.1-1_i386.deb.tar
(3.12 KiB) Downloaded 226 times

User avatar
saintless
Posts: 3862
Joined: Sat 11 Jun 2011, 13:43
Location: Bulgaria

#1964 Post by saintless »

Thank you, Fred!

I'm working on 021-apps-porteus.xzm now. There are some troubles I can not fugure out yet. Ktsus creates issues for user account for obshutdown for example. It does not give password window to reboot and shutdown Old gsu works.
Obshutdown Exit button also does not work for user from icewm and jwm.
There other small issues like loadmodule included in apt2sfs and loadmodule in 021-apps-porteus.xzm - they are different I think. I will overlay the last on top of the first one.

I will create new deb-porteus-dog-test.iso in the next days and very possible I will need your help for some issues.

Toni

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#1965 Post by fredx181 »

Hi Toni
Ktsus creates issues for user account for obshutdown for example. It does not give password window to reboot and shutdown
Strange, just tried, I don't have this problem.
Is the "gsu" line there in e.g. /usr/bin/wmpoweroff ?
Obshutdown Exit button also does not work for user from icewm and jwm.
Yes, got that also, appearently 'pkill X' or 'killall X' is not permitted for user.
A workaround I can think of is to NOT use obshutdown for JWM and have like this in ~/.jwmrc (instead of the Logout line I added for porteus-boot):

Code: Select all

<Program label="Reboot" confirm="false" icon="restart.png">wmreboot</Program>
      <Program label="Shutdown" confirm="false" icon="shutdown.png">wmpoweroff</Program>
And for icewm use obshutdown and in ~/.obshutdownrc instead of 'pkill X', then 'pkill icewm' (don't know, maybe is to much forcing)
(isn't there something like 'icewm -exit' ?, just couldn't find)
Hope this helps.
There other small issues like loadmodule included in apt2sfs and loadmodule in 021-apps-porteus.xzm - they are different I think. I will overlay the last on top of the first one.
Yes, the one in /usr/bin is old.
btw, now that my new loadmodule supports full path, maybe right-click option for (de)activate?
EDIT:
Q; What are you using as boot options for changes= ?
I suspect there there's a difference in how things behave according to what's used.

Fred

User avatar
saintless
Posts: 3862
Joined: Sat 11 Jun 2011, 13:43
Location: Bulgaria

#1966 Post by saintless »

Hi, Fred :)
snapexit_0.1.1-1_i386.deb + dialog.deb added in the main module. I tested changes=EXIT:/ and it works for user and root.
It creates folder /changes and I guess it adds more there after every reboot if we choose save?
I like DebianDog-PorteusDog shutting down logo :)
Strange, just tried, I don't have this problem.
Is the "gsu" line there in e.g. /usr/bin/wmpoweroff ?
Yes, the gsu line is there. I will check this again tomorrow. I use newer module than 01-v7.squashfs. It might be something I did.

Editing /home/puppy/.obshutdown.rc this way fixes all. No other changes needed:

Code: Select all

killall icewm jwm
We can add more WM names later if we need.

There other small issues like loadmodule included in apt2sfs and loadmodule in 021-apps-porteus.xzm - they are different I think. I will overlay the last on top of the first one.
Yes, the one in /usr/bin is old.
I think DebianDog does not have /usr/bin/loadmodule
We have your latest apt2sfs + loadmodule in /opt/apps/apt2sfs symlinked in /opt/bin
We have also /opt/bin/load-modules.sh used from SFS-Load
And now we have in 02-apps-porteus.xzm /usr/bin/loadmodules
Do you think we can use only the last one working for apt-2sfs and SFS-Loader?
btw, now that my new loadmodule supports full path, maybe right-click option for (de)activate?
I will try. Not sure how to do it for XFE yet but for Rox it should be easy.
Q; What are you using as boot options for changes= ?
I suspect there there's a difference in how things behave according to what's used.
I use it without option changes= mostly. Also tested changes.dat for user working.
Added also makepfile to replace /opt/bin/mk-save.gtkdialog in 02-apps-porteus.xzm

Tomorrow more testing and remastering :)

Toni

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#1967 Post by fredx181 »

Hi Toni
It creates folder /changes and I guess it adds more there after every reboot if we choose save?
Eh, if you made any changes, yes.
It's exactly like the graphical question to save or not, you get at shutdown from X.
EDIT: Maybe better use "changes=EXIT:/debian" to have it in same folder as where the 'base' folder is.
I like DebianDog-PorteusDog shutting down logo Smile
It's the original porteus logo (that shows on console) I stole and combined with simple debian logo. :)
killall icewm jwm
Good find, simplicity above all!
And now we have in 02-apps-porteus.xzm /usr/bin/loadmodules
Do you think we can use only the last one working for apt-2sfs and SFS-Loader?
"02-apps-porteus.xzm /usr/bin/loadmodule" I did mean that's old one.
They all work but the one included with apt2sfs is best IMHO, support full path to module, give message when error.

EDIT2: Sorry, wrong, the loadmodule script included with apt2sfs works ONLY for live-boot DebianDog.
So I'll make one for DebianDog-porteus later.

Good night Toni!

Fred

User avatar
sunburnt
Posts: 5090
Joined: Wed 08 Jun 2005, 23:11
Location: Arizona, U.S.A.

#1968 Post by sunburnt »

Wow... Too many posts to follow, I just noticed Toni`s about the menu.

# Script: debmenu-convert that converts debmenu files to a JWM menu file ( jwm.main ).
And a new caregories file to go with it: categories_debmenu.lst

# I can`t see why it errors about a missing double quote, but it makes a good menu file.

# Fred and all; All of my menu files go in $HOME/.jwm , except the script and exec. files.
This will change when I make it generate menus for IceWM as well.

EXPERIMENTAL... So the script writes no file, just xterm output.
To write a file use redirect: debmenu-convert > $HOME/.jwm/jwm.main

# It writes JWM menu entries for all apps listed the in debmenu files. 5 for XFE suite.

### I noticed that many debmenu files have no icon. So lots of editing is needed.
So lots of the menu items show the default icon.
### I also noticed the debmenu files have crappy categories. So more editing is needed.
Like Xhippo and Xrecorder both have Sound category, but this is for system sound settings.
So I`m slowly adding new and custom categories to: categories_debmenu.lst

# It shows the menu using the existing jwm.tail and .jwmrc, so it made a good file: jwm.main
Attachments
NEW_2-Items.zip
### /path/file
/opt/bin/debmenu-convert
$HOME/.jwm/categories_debmenu.lst
(2.06 KiB) Downloaded 172 times

User avatar
saintless
Posts: 3862
Joined: Sat 11 Jun 2011, 13:43
Location: Bulgaria

#1969 Post by saintless »

Hi, Terry.
# Script: debmenu-convert that converts debmenu files to a JWM menu file ( jwm.main ).
I know the posts are too many. I and William wrote a few times you are taking the wrong way if you try to use /usr/share/menu files for mk-jwm.menu.
One more time what I and William wrote:
We need your mk-jwm.menu to create menu from /usr/share/applications desktop files. This is the future menu method and most likely next debian stable will also create menus form desktop files. We need to fix and improve this menu method.

Creating Jwm and IceWm menu from /usr/share/menu files is working fine with the current official debian menu way. It has update-menus and install-menus scripts that check for new installed packages on several places inside .pid files. The process is stable and approved in the years. The categories are not the same as mk-jwm.menu makes but all debian packages in wheezy repository are created for this debian categories. Translating the categories in /usr/share/menu files will bring much more troubles in the future if we use mk-jwm.menu to create menu from /usr/share/menu files.
This is pure debian menu way and we need to keep it untouched in DebianDog. It is 100% working and tested in the years.

If we use mk-jwm.menu as default and it creates menu from /usr/share/menu files we gain nothing than different menu structure with very possible later issues with menu entry in wrong category.

If we use mk-jwm.menu to make menu from /usr/share/applications desktop files and try to improve this method, we will have separate working replacement for debian menu process. All linux goes this way - creating menu from desktop files. This is the future and this is the way DebianDog also should go.

If you insist to use /usr/share/menu files for mk-jwm.menu files for some reason then OK, but you will work on a menu method that will be history in a few years. And I think it will involve much more manual editing than the desktop files will need. Why we try to include Open Source Software Standards in DebianDog if mk-jwm.menu will not follow those standards?

Toni

mcewanw
Posts: 3169
Joined: Thu 16 Aug 2007, 10:48
Contact:

#1970 Post by mcewanw »

I agree wholeheartedly with Toni's above post Terry.

On another topic, but a much small matter: /opt/bin/gtkdialog3 should simply be a symbolic link to /usr/bin/gtkdialog
github mcewanw

User avatar
saintless
Posts: 3862
Joined: Sat 11 Jun 2011, 13:43
Location: Bulgaria

#1971 Post by saintless »

Hi, William.
mcewanw wrote:/opt/bin/gtkdialog3 should simply be a symbolic link to /usr/bin/gtkdialog
/opt/bin/gtkdialog3 should not exist at all with the current DebianDog configuration. Same goes for some files from live-boot v.2 in /usr/share/initramfs-tools.
They are included only in case we will try to use some files from Russian SFS-Puppy linux. They work only with this gtkdialog3 file. It was a while back but I remember I tested linking /usr/bin/gtkdialog and it did not work.
/opt/bin/gtkdialog3 file is older version of gtkdialog in DebianDog.

Toni

mcewanw
Posts: 3169
Joined: Thu 16 Aug 2007, 10:48
Contact:

#1972 Post by mcewanw »

saintless wrote:It was a while back but I remember I tested linking /usr/bin/gtkdialog and it did not work.
That's surprising. Yes, I noticed the /opt/bin/gtkdialog3 was an older gtkdialog (pre the thunor modded one).
github mcewanw

User avatar
saintless
Posts: 3862
Joined: Sat 11 Jun 2011, 13:43
Location: Bulgaria

#1973 Post by saintless »

Hi, All.

I'm going to upgrade XFE from v.1.32 to latest v.1.37
Latest version gives right click option custom scripts for files and folders. This makes possible easy to actvate/deactivate sfs modules for XFE + option similar to Open With and Custom Menu for all files and folders as we have in Rox.

Toni

User avatar
sunburnt
Posts: 5090
Joined: Wed 08 Jun 2005, 23:11
Location: Arizona, U.S.A.

#1974 Post by sunburnt »

Toni & William; I agree with what you`re saying. If Debian truly adopts desktop files...
I have received no reply to my post at the Debian forum. It`d be nice to hear it from them.

Seeing as Deb. menu files are kind of a mess and need lots of editing like desktop files.
The reality is that creating a new menu or desktop file is about as fast as editing one is.

So all the tools I`ve made are useful, but rapid "fixing" of desktop files is the most useful.

# I should improve the desktop file editor, and merge it with debmenu2desktop converter.

# A Name & GenericName translator to other languages would be real nice... How to do.

# We must refine the desktop categories file. Most of it comes from the FreeDesktop docs.

Toni; Does my debmenu2desktop converter work well.? Suggestions for it or mk-menu.?
I`ll dig back to your post about IceWM menu setup so mk-menu will make IceWM menus.
.

User avatar
saintless
Posts: 3862
Joined: Sat 11 Jun 2011, 13:43
Location: Bulgaria

#1975 Post by saintless »

Hi, Terry.
sunburnt wrote: If Debian truly adopts desktop files...
Even if Debian continue to use menu files it is no reason mk-jwm.menu to use the same files. just the opposite. We need to have a Open Source standards alternative to debian way or just keep using debian menu as it is. No use to have two methods on the same base - /usr/share/menu files.
Toni; Does my debmenu2desktop converter work well.? Suggestions for it or mk-menu.?
I can't tell you so fast it works well or not, Terry. it needs much more testing and installing new programs and testing again till we say no more need to inmprove it. It works but not tested enough to say lets automate it with mk-jwm.menu and use it as default for the next version. I need to spend few days only testing mk-jwm.menu and debmenu2desktop convert and installing new programs. No time to do this unfortunately.

Toni

User avatar
saintless
Posts: 3862
Joined: Sat 11 Jun 2011, 13:43
Location: Bulgaria

#1976 Post by saintless »

Terry,
I see in some desktop files category Utilities which does not go in Utility.
We need to change the convertion from menu file to point Utility instead Utilities or to make translation Utilities to Utility in categories.list. Or we have to change manual Utilities to Utility.

Toni

User avatar
saintless
Posts: 3862
Joined: Sat 11 Jun 2011, 13:43
Location: Bulgaria

#1977 Post by saintless »

Terry,
one more thing that might be important. While converting menu to desktop some desktop files does not get ; at the end. The category in mk-jwm.menu is not used if it does not have ; at the end.
It depends how ends the menu line. If it is like this:

Code: Select all

  section="Applications/System/Package Management" \  
it gets this desktop line:

Code: Select all

Categories=Applications;System;Package Management
If it is like this:

Code: Select all

section="Applications/File Management/" \
it gets right desktop line:

Code: Select all

Categories=Applications;File Management;
Can we do something to include translation in categories.list to move File Management in System for example and to translate Utilities to Utility?

Toni

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#1978 Post by fredx181 »

Hi Toni
Quote:
And now we have in 02-apps-porteus.xzm /usr/bin/loadmodules
Do you think we can use only the last one working for apt-2sfs and SFS-Loader?

"02-apps-porteus.xzm /usr/bin/loadmodule" I did mean that's old one.
They all work but the one included with apt2sfs is best IMHO, support full path to module, give message when error.

EDIT2: Sorry, wrong, the loadmodule script included with apt2sfs works ONLY for live-boot DebianDog.
So I'll make one for DebianDog-porteus later.
Looking at /usr/bin/loadmodule in 02-apps-porteus.xzm I see it's not old (I must be getting old :oops: ) )
So that's the one to use if you would implement right-click option for activate but that's only for DebianDog-Porteus then. (it mounts on /mnt/live/memory/images)

Fred

User avatar
saintless
Posts: 3862
Joined: Sat 11 Jun 2011, 13:43
Location: Bulgaria

#1979 Post by saintless »

OK, Fred.
I will use /usr/bin/loadmodule from 02-apps-porteus.xzm in DebianDog-PorteusDog-test.iso and It will have simlink to /opt/bin to change porteus loadmodule for porteus boot.
Just like /usr/bin/makepfile.sh creates link /opt/bin/mk-save.gtkdialog and we get porteus save file from the same menu entry with porteus boot.
Easy to be done.

We have right click load/unload option for SFS in XFE and Rox now. XFE is upgraded to latest version.

Toni

User avatar
sunburnt
Posts: 5090
Joined: Wed 08 Jun 2005, 23:11
Location: Arizona, U.S.A.

#1980 Post by sunburnt »

Hi Toni; I noticed desktop files having "Utilities", which is not in the FreeDesktop standard.
But I`ll add it to the categories.lst file ( I thought I had...). I think a lot of this is from Puppy.
I could add translations for Puppy`s custom setup: Categories=X-(AppName)

You`re right that Categories is supposed to have a ";" at the end. Many desktop files don`t.
I also removed the double quotes from the file. Odd that not quoting the value is standard.
Without them desktop files can`t be sourced in Bash. Seems they wanted it that way...

# I`ve got a new Desktop Menu Editor working, I`m waiting for info. from the guys at BaCon.

Here`s a new debmenu2desktop.convert file. I fixed the ";" and removed the double quotes.
# I tested it on the debmenu file: xfe and it output 5 groups of text for desktop files.
And also a new Categories.lst file that has the new translate line: "Utilities Utility"
Attachments
NEW_2-Items.zip
### Paths:
$HOME/.jwm/categories.lst
/opt/bin/debmenu2desktop.convert
(18.7 KiB) Downloaded 149 times

Post Reply