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

For talk and support relating specifically to Puppy derivatives
Message
Author
tigs
Posts: 39
Joined: Tue 05 Nov 2013, 23:47

#1546 Post by tigs »

fredx181 wrote: Did you try "changes=EXIT:/<path/to>/changes.dat" ?(changes.dat needs to be created first of course)
AFAIK the save file changes.dat is in fact the same as e.g. pupsave.4fs (behaves like a sfs module also)
But I don't know if it can be mounted read-only when write-protection is on.

Fred
Hi fred, I did use " changes=EXIT:/portdeb/debian/changes.dat". It can not not mount as "read-only" once write protection is on. here is the output (more or less) message during the boot:

Code: Select all

checking /mnt/sdb1/portdeb/debian/changes.dat
--------------------------------------------
fsck: read-only file system while trying to open /mnt/portedeb/debian/changes.dat
dist write-protected; use -n option to do a read-only check of the device
----------------------------------------------------
changes not writable, using memory instead
How to use the "-n option"

thanks

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

#1547 Post by mcewanw »

tony wrote:1. dtc-xen-firewall
2. apf-firewall
3. ipkungfu

I tried the first three and decided on ipkungfu.

It was easy to set up and produced a complex set of ip tables. I don't know enough to comment on the tables.

Drawback is no icon to check if it is running and needs to be set up to run at boot. If you are on a local network you will have to edit the tables to suit.

Regards Tony
I'm sure its a fine program, and certainly tiny, but is no longer supported and doesn't handle ipv6, which is bound to be needed some day.
github mcewanw

tony
Posts: 334
Joined: Sat 14 Jan 2006, 10:52
Location: Montreal.ca

#1548 Post by tony »

Thanks for giving me the opportunity to use this :-

Quis custodiet ipsos custodes?

Regards Tony

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

#1549 Post by mcewanw »

sunburnt wrote: As said, JWM is supposed to do multi desktop wallpapers all by itself, but it didn`t work for me.
I had multidesktop wallpapers done by JWM itself working okay, but the problem is it overwrites the rox pinboard background (you lose the pinboard). Without that rox problem the following in .jwmrc provides per desktop wallpapers (change image files to what you have). I tried it in Puppy: However, the way Tony is doing it (just like in icewm) doesn't suffer that rox conflict problem.

Code: Select all

<!-- Number of virtual desktops -->
<Desktops  width="4" height="1">
<Desktop Name="One">
<Background type="image">/usr/share/backgrounds/upup.jpg</Background>
</Desktop>
<Desktop Name="Two">
<Background type="image">/usr/share/backgrounds/lightblue.jpg</Background>
</Desktop>
<Desktop Name="Three">
<Background type="image">/usr/share/backgrounds/sunset_jesse.jpg</Background>
</Desktop>
<Desktop Name="Four">
<Background type="image">/usr/share/backgrounds/default.jpg</Background>
</Desktop>
</Desktops>
github mcewanw

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

#1550 Post by mcewanw »

EDIT: Ignore the below, I had another copy of live/01-v4.squashfs in another partition and that was getting loaded... The new 01-v5.squashfs is loading fine now.

Maybe I didn't get enough sleep last night but 01-v5.squashfs doesn't seem to be working for me (my download has the correct md5sum). When I boot with that in my 'live' folder, it seems to still load 01-v4.squashfs (which I have already deleted from my system...). DebianDog does boot as things stand, however, but when I open a terminal and enter 'man' or 'pman', it reports no such command and the menu is the old Debian one. It is probably something crazy I've done, but I can't find what? (I have deleted my live-rw, so that isn't the problem either...

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

multi-wallpapers not there by default at boot

#1551 Post by mcewanw »

re: the latest DebianDog squashfs.

Pressing desktop buttons does not change wallpaper on first boot. I think they should. Solution is to change line in $HOME/.desktop.conf from:

Code: Select all

Run=off
to

Code: Select all

Run=on
Furthermore, on my system at least, $HOME/.wallpapers/wallpapers.lst

uses 'Scale' which doesn't stretch out the background to fill my screen. I need to modify that replacing all occurrences of 'Scale' with 'Stretch'.

Toni, I also note that 'man' -> 'pman' is indeed working with browser H3V. However, from the code, it looks like if I install iceweasel as my default browser, man would still open H3V, which would be inconvenient. I haven't checked this in practice yet so could be wrong. pman should also have the defaultwebbrowser term changed to align with what term is used for that in DebianDog.

In regards to the above I'm still also wondering how the system will know that iceweasel becomes default_web-browser without manually arranging that. Or am I missing something about that.

I presume the method to achieve persistence remains for the moment as using one of using a live-rw file? Are you intending to offer options like Porteus-Wheezy has for using a simple changes directory as an alternative at some stage Toni?

Everything is certainly coming together nicely. Still to try JWM which I think is an exciting addition which should lower resource usage a little too.

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

#1552 Post by mcewanw »

Have now tried JWM in the latest DebianDog. Yes, the wallpaper switcher is working fine. Well done Toni!

Having said that... as you know we lose the Pager functionality in order to get the different desktop backgrounds without the Pager buttons. The Pager is however one of the advantages of JWM compared to iceWM, so the question is which is better - having a pager button that shows a representation in the button of what programs you have running on each desktop (albeit with each having a common background), or having no pager button but different background for each desktop?

As things stand, you could have windows open in various desktops but not realise that, whereas, with the pager buttons working you can see at a glance which desktops have windows open. I do miss that functionality. If only JWM's own ability to use different desktop backgrounds didn't overwrite rox pinboard (which it does according to my tests) because then you could have the best of both worlds (pager and different desktop backgrounds).

One small extra thing, is that personally I do rather miss being able to click the time indicator in order to bring up a calendar (as in Puppy and Winblows) - I never use osmo per se (preferring other apps for PIM) apart from for quick calendar in Puppy. I'm temporarily in Porteus-Wheezy right now and can't remember if hovering mouse over DebianDog time at least brings up an indication of the day and date.

EDIT: I'm back in DebianDog and note that hovering over Time display in taskbar does indeed provide day and date, which is great. That's was the main thing - I certainly wouldn't want the likes of osmo in the default release (which is a big package when downloaded my apt-get and, as I suggest, not necessarily a package most people would use anyway).

Otherwise JWM seems to be working fine (aside from, as you say Toni, the current need to ctrl-alt-f1 and enter startx to bring jwm up).
Last edited by mcewanw on Fri 28 Feb 2014, 05:39, edited 1 time in total.

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

Re: multi-wallpapers not there by default at boot

#1553 Post by saintless »

Hi, all.

Terry, thank you for the menu script. I will test it and write back.

William,
Pressing desktop buttons does not change wallpaper on first boot. I think they should. Solution is to change line in $HOME/.desktop.conf from:

Code: Select all

Run=off
to

Code: Select all

Run=on
[/url]
I prefer to keep it off. First it uses less ram and second I suspect auo-start wallpapers at boot created the issue I had with previous wallpapers.gui. At least I think it was related with replacing the wallpapers.gui while desktop.ctrl was active. I might be wrong but I prefer to play safe. I think is better the user to start wallpapers if needed.
Furthermore, on my system at least, $HOME/.wallpapers/wallpapers.lst

uses 'Scale' which doesn't stretch out the background to fill my screen. I need to modify that replacing all occurrences of 'Scale' with 'Stretch'.
I will change it to stretch. I guess it is fine with scale only on my computer.
I haven't checked this in practice yet so could be wrong. pman should also have the defaultwebbrowser term changed to align with what term is used for that in DebianDog.
I think adding links to default apps with puppy like names as you suggested will fix this. I will test it in the next days.
In regards to the above I'm still also wondering how the system will know that iceweasel becomes default_web-browser without manually arranging that. Or am I missing something about that.
I don't think every new installed web browser should auto-become default browser. Not sure for Iceweasel, but Firefox has Preferences option to check if it is default browser and change it every time Firefox run.
Do you have other suggestion instead manual default browser setup?
Are you intending to offer options like Porteus-Wheezy has for using a simple changes directory as an alternative at some stage Toni?
You can do it now by booting with this initrd:
http://www.smokey01.com/saintless/Light ... 0-4-486.xz
It becomes Porteus-DebianDog this way.
Similar if you boot with this initrd made from Fred for DebianDog:
http://www.smokey01.com/saintless/Light ... ux-live.xz
Try similar to this code for the last one:

Code: Select all

title lldeb (sda3/lldeb)
  root (hd0,0)
  kernel /lldeb/vmlinuz from=/lldeb
  initrd /lldeb/initrd.xz
The plan is to include both initrd (porteus and the default initrd1.img) for the beta version like in this testing iso:
http://www.smokey01.com/saintless/Light ... g-test.iso
Just not sure about separating the kernel module from the main module yet.

Toni

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

#1554 Post by saintless »

mcewanw wrote:Having said that... as you know we lose the Pager functionality in order to get the different desktop backgrounds without the Pager buttons. The Pager is however one of the advantages of JWM compared to iceWM, so the question is which is better - having a pager button that shows a representation in the button of what programs you have running on each desktop (albeit with each having a common background), or having no pager button but different background for each desktop?
I really prefer to have same wallpapers start-stop option for both WM. It will become very confusing for the user if we use different method for every window manager.
You can always put pager line back and remove the desktop.ctrl lines from system.jwmrc or $HOME/.jwmrc when we make it separate for user account.

Toni

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

#1555 Post by mcewanw »

saintless wrote:It will become very confusing for the user if we use different method for every window manager.
No problem and I see your point of view. However, I'll probably make them different on my system because for me any different wm (icewm, jwm, openbox etc) is by design different, with some advantages and some disadvantages.

The lowest resource wm DebianDog is currently providing is likely to be jwm (Lxtask suggests for me a couple of MB RAM saving) with common desktop background (which means I can modify the configs, like you suggest, to use Pager without any disadvantage on my system). I am really happy you have included JWM, Toni, and without it adding very much at all to the distribution size, especially since, as Terry mentioned, Joe Wingbermuehle, its creator is active on murga puppy forum and continually updates JWM according to feedback.

Still on the subject of JWM, I think, once tested, it will need a $HOME/.jwmrc or similar and the config thus in /etc/skel for multiuser use.

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

#1556 Post by saintless »

mcewanw wrote:as Terry mentioned, Joe Wingbermuehle, its creator is active on murga puppy forum and continually updates JWM according to feedback.
This is really big advantage for us. I hope we will manage to configure JWM but if we have a problem we can always ask him for help.

Toni

Edit:
Still on the subject of JWM, I think, once tested, it will need a $HOME/.jwmrc or similar and the config thus in /etc/skel for multiuser use.
Yes, this will be done once we have JWM as we like.

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

#1557 Post by saintless »

sunburnt wrote:I made a menu-root.lst file that sets the root-menu`s categories.
And a categories.lst file that matches and translates categories found in desktop files to a root-menu category.
Hi, Terry.
I see mk-menus gives menu output in terminal but I can't make it to change the real start menu. I use all files in /opt/bin or from separate menu folder. What should I do to make the changes to appear in start menu?

Toni

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

Re: multi-wallpapers not there by default at boot

#1558 Post by saintless »

mcewanw wrote:Solution is to change line in $HOME/.desktop.conf from:

Code: Select all

Run=off
Hi, William.
Just noticed you edit the .desktop.conf file with text editor if I understand right.
Use the desktop icon or Start menu for Wallpapers to start the GUI from Terry. Start/Stop will rewrite .desktop.conf file. Check/uncheck Run on boot will create/delete symlink in $HOME/Startup and you also can scale/strech the image.

Toni

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

Re: multi-wallpapers not there by default at boot

#1559 Post by mcewanw »

saintless wrote:
mcewanw wrote:Solution is to change line in $HOME/.desktop.conf from:

Code: Select all

Run=off
Hi, William.
Just noticed you edit the .desktop.conf file with text editor if I understand right.
Use the desktop icon or Start menu for Wallpapers to start the GUI from Terry. Start/Stop will rewrite .desktop.conf file. Check/uncheck Run on boot will create/delete symlink in $HOME/Startup and you also can scale/strech the image.
Oh, I see. Thanks Toni.
github mcewanw

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

#1560 Post by saintless »

mcewanw wrote:The Pager is however one of the advantages of JWM compared to iceWM, so the question is which is better - having a pager button that shows a representation in the button ...
Hi, William.
Just for information experimenting with preferences file for IceWM shows there is no advantage for JWM regarding presentations in pager buttons.
Edit $HOME/.icewm/preferences this way:

Code: Select all

#  Show workspace switching buttons on task bar
TaskBarShowWorkspaces=1 # 0/1

.....................

#  Show a mini desktop preview on each workspace button
PagerShowPreview=1 # 0/1
Toni

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

#1561 Post by mcewanw »

saintless wrote:

Code: Select all

#  Show workspace switching buttons on task bar
TaskBarShowWorkspaces=1 # 0/1
.....................
#  Show a mini desktop preview on each workspace button
PagerShowPreview=1 # 0/1
Hi Toni, the above info you give are good icewm options to know. I may use these.
github mcewanw

anikin
Posts: 994
Joined: Thu 10 May 2012, 06:16

#1562 Post by anikin »

Hi saintless et al,

Don't know if the following is of any relevance ... for what it's worth:
JWM v2.2 Release Notes wrote:Configuration Changes
...
JWM no longer allows custom window buttons. These buttons are now custom drawn to an appropriate size using X graphics primitives.
The information in TrayButtonStyle is now inherited from TrayStyle instead of TaskListStyle. This means that tray buttons now get defaults from the tray instead of from the task list. In addition, it is now possible to specify ActiveBackground and ActiveForeground in TrayStyle. This makes it possible to set defaults for both tray buttons and task list buttons in TrayStyle.
read more here >>>http://joewing.net/projects/jwm/release-2.2.shtml
... as I'm severely biased in favor of JWM, I applaud the meticulous work, you guys are doing on its configuration.

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

#1563 Post by saintless »

Thanks, Anikin.
If there is no way to create TrayButton it means we loose Wallpapers.GUI if we update Jwm to v.2.2
Anyway we use v.2.1.0.3 so it is newer enough and last version in debian stable, testing and unstable. I don't think we need to move to v.2.2 and start configuring the changes again.

BTW I forgot to mention almost all theme settings in JWM are from here:
http://antix.freeforums.org/jwm-theme-f ... t3336.html

Toni

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

#1564 Post by mcewanw »

saintless wrote:Thanks, Anikin.
If there is no way to create TrayButton it means we loose Wallpapers.GUI if we update Jwm to v.2.2
I'll have to try it sometime, but I think it means window decoration buttons not traybuttons. The opportunity to create traybuttons may not be effected I feel.
github mcewanw

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

#1565 Post by mcewanw »

By the way Toni, DebianDog cpu freq scaling is now working out the box on my Pentium M based system. Uses ondemand governor.

Post Reply