Puppy Linux Discussion Forum

[saintless]

Hi Fred.

[mcewanw]

You do realize, Fred and Toni, that you've discussed the, somewhat major I feel, difference between openbox and jwm /etc/profile PATH handling before. I can't remember where exactly, but been long time ago I know.

I have to say, I don't think user and root 'should' have the same default PATH (why should a normal user have access to executables in /sbin, for example). But main thing is that this difference seems to come back to haunt developments in the sense that scripts developed on openbox version sometimes it seems have problems on jwm DD/MintPup etc.

I think you can tell my opinion - the scripts should be written on the basis of the user default PATH not having access to admin binaries, but easy for me to say. More generally, it appears from reading these repeating problems that the jwm and openbox versions would be easier to maintain if underlying system configs were kept identical (aside from wm configs etc). I use both jwm and openbox versions at home, and I do generally run as root user, but that's only because I'm being lazy - I keep intending moving over to normal user most of the time, if only because running as root user encourages poor use of access control rights (appropriate file/dir permissions included) which is certainly a big no no in professional circles, and bad from an app developer's point of view since what works as root may turn out not to work as a normal user on big Linux systems.

William

EDIT: For the sake of balance, please let me also say that in terms of look and feel and pleasure in usage, the DD-openbox is the nicest, IMO... That is probably because openbox allied with xfdesktop and Thunar is such a pleasant combination - so no surprise to me that a non-technical user such as my partner likes that one the best. I'm a bit different though - I'm really into low resource usage at the expense of some of the 'niceties' and I also think JWM isn't too bad once tweaked a bit (I just haven't bothered since what is there is fine for me). And Rox is also very efficient (running several Rox filers doesn't seem to increase overall Rox resource usage much at all - basically once Rox pinboard is running, that seems to pretty much determine most all resources Rox ever uses... amazing really). But most modern systems have 'tons' of resources, so worrying about a few MB RAM here and there isn't probably very important to most people (even my 'newer' machines, the HP elitebooks, are from 2009 and have 2GB RAM for example - plenty for most of the junk I do no matter which of the DD or MintPup systems I'm running :-) But keeping normal user access controls as tight as big brother Debian/Ubuntu/Mint seems pretty important to me (despite the oft-discussed views of the Puppy Linux world more generally).

[saintless]

[fredx181]

[saintless]

Hi Fred.
I prefer to change less as possible. Changing the content of one file only ( /opt/bin/gsu-root) is the best way to go. Attached gsu-root in archive if you like to continue the testing with this script. It is gsu-notimeout with added -E.
When I'm ready with the testing I will upload new remaster-scripts with /opt/bin/gsu-root included and new install scripts package.

BTW I had one situation when remasterdog and remastercow do not work because some process from previous remasterdog or remastercow is still active. There was error about /dev/sda1 is already mounted according the information in /etc/mtab. The error message is visible after removing 2> /dev/null from mount /dev/$DRV /mnt/$DRV 2> /dev/null line. I'm not sure yet if this could be a problem but I think you can reproduce it by opening second remasterdog while the first one is still active copying files. I will test this situation more.

Edit: It works for me starting remasterdog and remastercow at the same time now. Maybe I did something else to cause this error. I will try to reproduce it later.

Toni

[fredx181]

[fredx181]

Hi everyone,

*** New openbox-mintpup light setup ***

Thanks to the suggestions from William for using rox-pinboard!.
There's choice now to use rox-pinboard or tint2 left-panel for providing the desktop (see below and screenshots)

As I didn't want to change any existing settings for rox, there's one annoying thing:
The iconified windows from rox-pinboard are (for a part) under the conky window.
To disable iconified windows go in rox options and uncheck "Show iconified windows"

Info:
(see also README-setup in the extracted openbox-mintpup_setup-0.0.2.tar.gz)
-------------------
Openbox-mintpup setup, version 0.0.2.

Changes:
- Very much improved menu, it reads now from /etc/xdg/menus/mintpup-ob-applications.menu.
It's a modified /etc/xdg/menus/xfce-applications.menu
It looks similar to the menu in DebianDog Openbox_xfce version.

- Choice of 2 desktop types:
-- Rox pinboard, desktop provided by rox, with launcher icons, tranparent conky, tint2 bottom panel.
-- Tint2 transparant left-panel with launcher icons, tranparent conky, tint2 bottom panel.
To switch between them: Menu > Desktop Manager
Wallpaper chooser (Menu > Set Wallpaper) is different for Rox pinboard and Tint2 transparant left panel;
for tint2 panel it's nitrogen, for rox-pinboard it's the wallpaper gui program from Terry, just like on JWM.

To install: (can be installed over previous version 0.0.1, will overwrite old configuration in ~/.config/openbox when running 'Start Openbox' from menu):

After apt-get update :

FIRST: Install tint2_0.11+svn20121014-3_i386.deb:
This tint2 version is from Debian Jessie, the Ubuntu Trusty tint2 version is to old.

From terminal in this directory:
dpkg -i tint2_0.11+svn20121014-3_i386.deb
And:
apt-get -f install

THEN:
Install openbox-mintpup_0.0.2_i386.deb:

From terminal in this directory:
dpkg -i openbox-mintpup_0.0.2_i386.deb
And:
apt-get -f install

Total install size: around 9 MB

To start: Jwm menu > System > Start Openbox
To get back to Jwm from Openbox: Menu > Settings > Start Jwm

When installing from previous version installed while inside Openbox-mintpup session, upgrade to 0.0.2 by running Menu > Settings > Start Openbox.
Warning: this will overwrite the configuration in ~/.config/openbox
--------------------------
Download:

Edit: Link to openbox-mintpup_setup-0.0.2 removed, since it conflicts with new package jwm-obmenu (Menu Openbox for Jwm) if openbox-menu is activated.
Replaced by version 0.0.3, conflicting has been fixed.
https://googledrive.com/host/0ByBgCDlZZ8K5bUsxVnhCTkhoZDA/openbox-mintpup_setup-0.0.3.tar.gz

Toni, I really didn't want not interfere with JWM session, and I think I succeeded with that. except one thing:
In ~/.config/rox.sourceforge.net/ROX-Filer/globicons some icon paths are added (e.g. for conkytoggle), it doesn't show anything from that on JWM or Icewm though.

Edit2:
openbox-mintpup is now part of the mintpup repository, so to easy install, just in terminal:

[saintless]

Hi Fred.

The link in the first post changed to your new openbox setup.

DebDog repositories updated with mpv, youtube-viewer, debdoginstallscripts_1.0.5_i386.deb, remaster-scripts_1.0.4_i386.deb with latest progressbar fixes and changed gsu-root. I will make updated packages for MintPup later. Fixes post for Wheezy and Jessie updated.

I can't reproduce again the problem I had with not working remastercow and remasterdog after the message sda1 already mounted. If it happens again in the future (it was with live-boot-3 no persistence) I will try to get more information before reboot.
I don't think the testing is enough yet for remastering and install scripts changes but all looks OK so far testing with all boot methods on my machine.

Toni

[futwerk]

some new backgrounds.

[saintless]

[mcewanw]

[mcewanw]

I don't myself have any particular favourite desktop, but I'm trying a psychological experiment by using the following on my partner's machine. I am testing my theory that it is not openbox or jwm differences that makes her like DD_openbox_wheezy look and feel the most. Rather, I suspect it is simply the wallpaper used and desktop icons placed vertically and horizontally rather than the Puppy-like traditional triangular desktop icon placing, which I also find somewhat ugly. We shall see ;-)

Note in my screenshot below (using MintPup jwm) I've not only adopted Fred's openbox_wheezy wallpaper but also made the taskbar icons a max of 32 bits (to look similar to Fred's current MintPup_openbox). i.e. I've modified the following ~/.jwmrc line 186 from:

[saintless]

[mcewanw]

Ah, thanks Toni for explaining how jwm menu gets processed. Now that
you've mentioned it I think I recall similar arrangement in Puppy itself. Anyway, modified jwm.tail now with same code change and all fine following my running menu-puppy and restarting jwm.

I imagine Fred will tackle the extra xterm issue for openbox version - I guess the 'proper' solution would be to change one of Terry's scripts (or a new intermediate script) to honour the exec from terminal line, but maybe a bit tricky.

William

EDIT: without having checked the source, I currently presume mk-jwm.main is the main menu creation script, which I guess is in BaCon.

[saintless]