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

[mcewanw]

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).

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?

[sunburnt]

NOPE... Still not working right.

[mcewanw]

Just trying Terry's menu in JWM for the first time. It is looking good!

[saintless]

Toni; Do you know if IceWM does search sub dirs. for icons.?

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.

Toni

[saintless]

Hi, William.

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 ... ux-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

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 ... nitrd1.img
You need to change persistent with peristence in kernel boot line and to use this save file:
http://www.smokey01.com/saintless/1Gb-p ... ive-rw.zip

Toni

[mcewanw]

Hi, William.

DebianDog is pure Debian and it will use debian initrd by default

Yes, it is important to have the pure Debian version by default. Very nice to have all these options though. Well thought out scheme.

[saintless]

Toni; For help, run: /root/0_BaCon/debmenu2desktop
This command filled /tmp/0 with only 66 ready to go desktop files ( not sure why not 70 ).

Code: Select all

# /root/0_BaCon/debmenu2desktop /usr/share/menu /tmp/0

        #####  Total Files:  70
#

Hi, Terry.
debmenu2desktop is setup to use /mnt/sq/usr/share/menu which makes it not to work on DebianDog. I guess you use it from puppy?
I had to make some changes but works fine now. We will include it as menu entry option.
Added this in the beginning of /opt/bin/debmenu2desktop (otherwise gives error there is no /tmp/0 folder):

Code: Select all

mkdir /tmp/0
echo "***All converted desktop files are in /tmp/0 folder.***"

And the path changeed from:

Code: Select all

Fs=`find /mnt/sq/usr/share/menu -maxdepth 1 -type f |grep -v README`

to to this:

Code: Select all

Fs=`find /usr/share/menu -maxdepth 1 -type f |grep -v README`

Here is the output from DebianDog now:

Code: Select all

root@debian:~# debmenu2desktop /usr/share/menu /tmp/0
***All converted desktop files are in /tmp/0 folder.***

        #####  Total Files:  70
root@debian:~# 

Toni

[saintless]

Hi, all.

After installing w3m and links2 I get in /usr/share/menu files for links2 (GUI), Links2 (CLI), w3m (CLI) and I can start them all from start menu.

In /usr/share/applications I get desktop file only for Links2 (GUI).
If this is the case for most text based programs that means the user have to convert desktop files for them all the time to make them appear in the menu.

It seems desktop files are not well supported in debian package repository. I think we need a way to automate the process of converting menu to desktop files and move them in /usr/share/applications to make them appear in the mk-jwm.menu after installing every new package.

Toni

[fredx181]

William, here's a new 021-apps-porteus.xzm updated for JWM.
Just replace with this one in the 'base' folder.
changes=EXIT:/ and choice to save or not should work then.
https://drive.google.com/file/d/0ByBgCD ... sp=sharing

Toni,
Just for info: I edited /root/jwm/jwm.tail and /etc/jwm/system.jwmrc.
Removed the "shutdown" and "reboot" entries and added "Logout" pointing to obshutdown.
Terry, I'll test your new menu-maker later today.

Fred

[saintless]

William, here's a new 021-apps-porteus.xzm updated for JWM.
Just replace with this one in the 'base' folder.

Thank you, Fred!
Downloading and saving this for the new iso build.

Toni

[fredx181]

William, here's a new 021-apps-porteus.xzm updated for JWM.
Just replace with this one in the 'base' folder.

Thank you, Fred!
Downloading and saving this for the new iso build.

Toni

You are welcome Toni!
I hope I did it right, also for puppy user and /etc/skel.
Please test a little.

Fred

[fredx181]

Hi William, Toni
New revision of 021-apps-porteus.xzm:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
Forgot in previous version to update a few scripts to use 'gsu' (Graphical su) for multiuser support.

Toni, what I didn't add is a menu entry for creating porteus savefile (anyway question will appear at shutdown to create savefile in case booting without one)
It would be nice if you can add, but if it's very complicated just leave it like it is.

Fred

[saintless]

Toni, what I didn't add is a menu entry for creating porteus savefile (anyway question will appear at shutdown to create savefile in case booting without one)
It would be nice if you can add, but if it's very complicated just leave it like it is.

Thank you, Fred!

I will add porteus save file option with sure.
I'm removing the second pae kernel now and I will start working on the separate kernel modules.
The base will be one module with kernel 486 included. This way only one module will be loaded on boot for Debian boot and 2 modules for Porteus boot. It should not take more ram usage this way.
The modules for 686-pae and Porteus-kernel + more extra modules later will be available for download and remastering the main module after purging 486 kernel.

Toni

[sunburnt]

Everyone;

Just for info: I edited /root/jwm/jwm.tail and /etc/jwm/system.jwmrc.
Removed the "shutdown" and "reboot" entries and added "Logout" pointing to obshutdown.

I think that this jwm.tail file should be the one for normal users. Correct.?
For root user having the Shutdown, Reboot, etc... is a good thing. Right.?
# We need to define root & user menu differences.

Toni; Yes... I keep forgetting to remove PRINT statements and other code patches.

# Instead of /tmp/0 , probably better to use something like: /tmp/desktop

# How about mk-jwm.menu checking for changes in: /usr/share/menu
This can be done by file creation or a tracking list.
If there`s a change, then run ( on all new files found ):

Code: Select all

debmenu2desktop /usr/share/menu/(NewFile) /usr/share/applications

### New mk-jwm.main file. Complete rewrite of the icon search.
Finds icon anywhere in /usr/share/icons, and it made a good menu.
# Icon search method:
1) If no Icon= , then default icon
2) If is good: /path/icon.ext
3) If is good: $HOME/.icons/icon.ext
4) If is good: /usr/share/pixmaps/icon.ext
5) Search icon no ext. in: $HOME/.icons
6) Search icon no ext. in: /usr/share/pixmaps
7) "find" icon in: /usr/share/icons

[saintless]

Hi, Terry.

Just for info: I edited /root/jwm/jwm.tail and /etc/jwm/system.jwmrc.
Removed the "shutdown" and "reboot" entries and added "Logout" pointing to obshutdown.

I think that this jwm.tail file should be the one for normal users. Correct.?
For root user having the Shutdown, Reboot, etc... is a good thing. Right.?

No, this is something needed for Porteus boot option to make save changes work. The changes will be in very small separate module used only for Porteus boot.
Root and user will get the same jwm.tail with shutdown submenu.

# How about mk-jwm.menu checking for changes in: /usr/share/menu
This can be done by file creation or a tracking list.
If there`s a change, then run ( on all new files found ):

Code: Select all

debmenu2desktop /usr/share/menu/(NewFile) /usr/share/applications

Sounds good to me.

### New mk-jwm.main file. Complete rewrite, finds icon anywhere in /usr/share/icons
It does "find" on: /usr/share/icons , it did find an icon file there and made a good menu.

Thank you, Terry! I will test it and report back.

Toni

[sunburnt]

Toni; Joe was right about the Firefox navigation keys.
They`re probably the same for other Mozilla browsers too.
Comment out these lines at the bottom of the jwm.tail file:

Code: Select all

<-- 
   <Key mask="A" key="Left">ldesktop</Key>
   <Key mask="A" key="Right">rdesktop</Key>
 -->

### I`ll look at doing a new file find in /usr/share/menu

# Fred; Maybe you have an idea as to how to find new menu files.?

I didn`t catch that the menu change was a "Proteus thing".

### But still... We want to sandbox the user menu, right.?
.

[saintless]

### New mk-jwm.main file. Complete rewrite of the icon search.
Finds icon anywhere in /usr/share/icons, and it made a good menu.
# Icon search method:
1) If no Icon= , then default icon
2) If is good: /path/icon.ext
3) If is good: $HOME/.icons/icon.ext
4) If is good: /usr/share/pixmaps/icon.ext
5) Search icon no ext. in: $HOME/.icons
6) Search icon no ext. in: /usr/share/pixmaps
7) "find" icon in: /usr/share/icons

Thank you, Terry!
Seems working fine. I get icon for audacious without changing anything else than your new mk-jwm.main
I will test it more in the next days to see if I can find any problems.

Toni

[fredx181]

Terry,

I didn`t catch that the menu change was a "Proteus thing".

It's "Porteus"
You should try it once, then you know what we're talking about and you might like it!
It brings a lot of options more than the regular debian live-boot and the debian system itself is exactly the same.

Toni, still struggling with multiuser support with 021-apps-porteus.xzm.
It's the exact thing as some time ago:
Because of the copying when changes=EXIT:/ option is used /home/puppy is owned by root.
I thought I had solved it but can't remember how
So probably again new update will come later.

Fred

[saintless]

Because of the copying when changes=EXIT:/ option is used /home/puppy is owned by root.
I thought I had solved it but can't remember how
So probably again new update will come later.

Fred, I'm not sure if this is what you are looking for but check out in 01-v7.squashfs in /opt/bin/new/changes-EXIT-files
I keep there to be added later the latest files from you uploaded after creating DebianDog-PorteusDog-test.iso

Toni

[saintless]

### But still... We want to sandbox the user menu, right.?
.

I'm thinking to keep root only applications to be executed from command line (like xdm-start and xdm-stop). This will save as the troubles creating separate jwm menu for user. User and root will have the same JWM menu unless we do not find good reason to keep them different.

What I don't like is after installing xdm the path in /etc/profile does not work and we have path exported from /etc/environment
Unfortunately it exports the secure bin paths for user also. I will try to fix this but for now we keep this problem.

Toni