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

[saintless]

Hi, Emil.
Multiuser is new area for me but from what I learned - yes.
Everything in /etc/skel will be included in /home/hew-user with owner new-user

so if you put it into root and in the skel dir then every user can customize its own tray.

Yes, just copy from /root to /etc/skel all you like every user to have.
Regarding the tray the user will have to modify /home/user/.icewm/startup to make the tray looks different.

Toni

[saintless]

Also what I would like in porteus-boot version is in icewm-menu an entry for special porteus-savefile-create instead of live-rw create, now there's only the prompt for it at shutdown

Hi, Fred.
I think all I need is to use /usr/bin/makepfile.sh from Porteus-Wheezy
Is there anything else I should copy to make porteus save file work?

BTW while experimenting I loaded main puppy.sfs module with SFS-loader in DebianDog and this broke the live-rw save file.
I see Porteus-Wheezy have right click load / unload module options. Maybe warning to be careful right clicking on main puppy sfs modules will be useful in load module right click option.

Edit: Thank you for RemasterCow script. I need to test it few days and clear my vision about what changes will be needed.
In porteus boot DebianDog-PorteusDog.iso /live/cow is symlink to /lib/live/mount/changes so remstercow should work for both boot methods.
This is also very good option for DebianDog and Porteus-Wheezy to have snapshot only with the changes without remastering the main module.
Toni

[fredx181]

Hi Toni

fredx181 wrote:
Also what I would like in porteus-boot version is in icewm-menu an entry for special porteus-savefile-create instead of live-rw create, now there's only the prompt for it at shutdown

Hi, Fred.
I think all I need is to use /usr/bin/makepfile.sh from Porteus-Wheezy
Is there anything else I should copy to make porteus save file work?

No, the makepfile.sh script is the one.

Tried your last version and all seems to be ok.
Tried boot option "changes=EXIT:/<pathtochangesfile>": working fine also.
The mountlink script runs well now and you might have noticed already: /mnt/home and /mnt/saved symlinks.
/mnt/home is in fact the same as /live/image and /mnt/saved same as /live/cow.
When boot option "changes=EXIT:/<pathtochangesfile>" is used: /mnt/saved is symlink to:
/mnt/live/memory/images/changes-exit
Without the EXIT: changes boot option: /mnt/saved is symlink to /mnt/live/memory/changes
(this is what the mountlink script takes care of)
So what I'd like to suggest is that /live/cow becomes symlink to /mnt/saved
Then both changes options work for the remastercow script.

DebianDog-Beta version almost ready I think!

EDIT:

BTW while experimenting I loaded main puppy.sfs module with SFS-loader in DebianDog and this broke the live-rw save file.
I see Porteus-Wheezy have right click load / unload module options. Maybe warning to be careful right clicking on main puppy sfs modules will be useful in load module right click option.

yes, I agree, will look into that.

Fred

[fredx181]

Hi Toni
Trying out puppy user now:
First went perfect but after reboot with savefile I get this when changing desktops:

Code: Select all

Error saving pinboard /home/puppy/.config/rox.sourceforge.net/ROX-Filer/pinbd: Permission denied

EDIT: there is problem when with porteus version "changes=EXIT:" is used when running as puppy user.
When rebooting it depends on /usr/bin/wmreboot>save2flash>snapmergepuppy.
The last needs to write to /mnt/live/memory/images/changes-exit which I think only root can do.
Maybe also the "su root" option ?
I'll think about this more.

Fred

[saintless]

Hi, Fred.
Thank you for testing the save options for porteus boot. I tried to follow your instructions and the changes in porteus kernel module with yad and obshutdown you made for DebianDog. Glad to read all is OK this time.

So what I'd like to suggest is that /live/cow becomes symlink to /mnt/saved
Then both changes options work for the remastercow script.

Yes, I will do that. Maybe /live/image link to /mnt/home also will be better.

DebianDog-Beta version almost ready I think!

Not yet i think but we are much closer.

Trying out puppy user now:
First went perfect but after reboot with savefile I get this when changing desktops:

Code: Select all

Error saving pinboard /home/puppy/.config/rox.sourceforge.net/ROX-Filer/pinbd: Permission denied

Thank, I will look at this. I know Terry makes new wallpapers script + GUI. It will be changed soon but I will see way is this error.

Toni

[fredx181]

Hi Toni

Quote:
DebianDog-Beta version almost ready I think!

Not yet i think but we are much closer.

Yeah, some more to do with the multi-user support.
Did you see my edit in previous post?

Fred

[saintless]

EDIT: there is problem when with porteus version "changes=EXIT:" is used when running as puppy user.
When rebooting it depends on /usr/bin/wmreboot>save2flash>snapmergepuppy.
The last needs to write to /mnt/live/memory/images/changes-exit which I think only root can do.
Maybe also the "su root" option ?
I'll think about this more.

Thanks, Fred. I prefer user not to have rights to create save files unless the root password is typed to give permission. Save file is used in boot for all users and should be created only with root permissions.
su-to-root option is good solution for this.

Toni

[fredx181]

Hi Toni

Thanks, Fred. I prefer user not to have rights to create save files unless the root password is typed to give permission. Save file is used in boot for all users and should be created only with root permissions.
su-to-root option is good solution for this.

I see what you mean but there's little misunderstanding I think:
The wmreboot/wmpoweroff>save2flash>snapmergepuppy sequence is not for creating savefile but for copying the changes to the savefile at shutdown (but first have the choice to save or not.)
For me this very important this EXIT: function because it's just the extra option that live-boot doesn't have(and puppy has it also:pupmode=13)

So for running as normal user I have the following in mind:
Set it up exactly like you did with remasterdog (and others) so you get in PATH:
- wmpoweroff-start
- wmreboot-start
So these will then run wmpoweroff or wmreboot after entering root password.
Then in /home/puppy/.obshutdownrc: (and probably also in /etc/skel/.obshutdownrc)
- wmpoweroff-start instead of wmpoweroff
- wmreboot-start instead of wmreboot
What do you think?

Some more problems testing puppy user :
As I said first time logging in went smooth but after couple of reboots with savefile the problems came
Now I get this after typing startx:

Code: Select all

xauth: timeout locking authority file /home/puppy/.Xauthority

Then when pressing Ctrl+c a couple of times X will start

Regards
Fred

[saintless]

So for running as normal user I have the following in mind:
Set it up exactly like you did with remasterdog (and others) so you get in PATH:
- wmpoweroff-start
- wmreboot-start
So these will then run wmpoweroff or wmreboot after entering root password.
Then in /home/puppy/.obshutdownrc: (and probably also in /etc/skel/.obshutdownrc)
- wmpoweroff-start instead of wmpoweroff
- wmreboot-start instead of wmreboot
What do you think?

Hi, Fred. Sounds fine solution for me. I will do it this way.

Some more problems testing puppy user :
As I said first time logging in went smooth but after couple of reboots with savefile the problems came
Now I get this after typing startx:

Code: Select all

xauth: timeout locking authority file /home/puppy/.Xauthority

Then when pressing Ctrl+c a couple of times X will start

Thanks, I will look at this also later. I did quick test with live-rw save file and I didn't get this errors for puppy user but I will test it proper in the next days and use porteus changes.dat file as well.
I like to experiment with RemasterCow for a day or two first to make clear for my self what exactly is needed regarding separate kernel module.

Everyone, please. post all problems you have from your tests till then.

Toni

[fredx181]

xauth: timeout locking authority file /home/puppy/.Xauthority

Then when pressing Ctrl+c a couple of times X will start Rolling Eyes

Sorry Toni, I just see now that /home/puppy is owned by root
This is caused by the saving on EXIT only.
So forget about the previous problems I mentioned about running as puppy user.
So I'll have to find a way to adjust it to multi-user support.

Fred

[sklimkin]

Hi All!

keyboard-switcher for Eng--NoEng keyboard layots
remark:
I have raised the issue of switching keyboard layouts for non-English speakers.
I understand that many here do not need such an opportunity.
But I hope that this opportunity will draw attention to the installation of new people.

Gestures for this quite a bit:
# apt-get update
# apt-get install xxkb - 221 KB of disk space
# dpkg-reconfigure keyboard-configuration
// I select then (for me ru_RU):
// generic 105-key
// Russian
// Control+Shift
// No temporary switch
// No AltGr key
// No compose key
// Use Control+Alt+Backspace to terminate X server - Yes

edit file /etc/X11/app-defaults/XXkb
------------------------------------
XXkb.mainwindow.enable: yes - see strings 6,8,9,10,11
XXkb.mainwindow.type: tray - see string 24
XXkb.button.enable: no - see string 27

// all country-flags in /usr/share/xxkb
//new item: Menu--Programs--Applications--System--Administration--xxkb

// start xxkb in background:
# xxkb &

What comes out of it:
In 'Light-Debian' works, the icon appear in the system tray.
In 'Porteus-Wheezy' does not work, but the icon appears in the system tray.

Toni and Fred. If you think it possible, then add xxkb
I do not want to "pull the blanket over himself," so you can add German and flag of Germany (to me at school like German umlauts).

Sergey.

[saintless]

Toni and Fred. If you think it possible, then add xxkb
I do not want to "pull the blanket over himself," so you can add German and flag of Germany (to me at school like German umlauts).

Thank you very much, Sergey You teached DebianDog to speak Russian as I read
This is great option to have language swith icon on taskbar and we will include xxkb.
Thank you for shareing this. It is not easy for every user to find out how to edit /etc/X11/app-defaults/XXkb and make it work.

Strange it does not work in Porteus-Wheezy. I will test it also in the next days. Maybe there is a missing package?

Sergey, you maybe will be interested from another project for auto building debian small icewm system with bulding script. Similar to what you use for LXDE debian iso.
http://www.murga-linux.com/puppy/viewtopic.php?t=91832

Toni

[saintless]

This is caused by the saving on EXIT only.
So forget about the previous problems I mentioned about running as puppy user.

Thank you, Fred.. I will think about multiuser on EXIT save changes as well.

[fredx181]

Hi Toni
Here some replacements of files that should make the porteus changes=EXIT:/... option work for puppy user and hopefully for whole multi-user support:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
As much as possible I've placed the files in the appropriate folders but I assume the replaced /home/puppy/.obshutdownrc needs to be made owned by puppy user.
(This multi-user thing is rather new to me also)
I've tested again running as puppy user: Nothing wrong with it, great work!

Fred

[saintless]

https://drive.google.com/file/d/0ByBgCD ... sp=sharing

Thank you, Fred.
I will include them in the 021-apps-porteus.xzm

Toni

[sklimkin]

Hi Toni,

Toni: Sergey, you maybe will be interested from another project for auto building debian small icewm system with bulding script.

I have read everything there and looked.
This could be useful (partially) at the beginning of the creation of Light-Debian.
For example, some fragments of scripts from Debian-light-builder.tar.gz
But now we have gone too far (and successfully), to go back.
I do not like live-boot ver. > 2.0.15 because it focuses only on one monolithic squashfs-module.
(I see that in the Light-Debian now live-boot version 3.0.23.1 but I missed something, and I continue to refer to it as 2.0.15, sorry).
It is difficult to predict what else will come up mr.Baumann - so I think live-boot is not the best tool to work with squashfs-modules. Poor also the fact that he is the only such a tool for Debian (and in Ubuntu it even worse).

Illusion called "Auto" disappears when start adding to the base-module for more things. Xorg + any-WM already contain some ambiguity = problem.

I enjoy the work of Fred in which he successfully integrated capabilities Porteus and do not hurt Debian.
I will say more: we now use quite a bit of what they allow "cheatcodes Porteus" to boot command line. Those opportunities are immense, but for us to use them will be relevant probably a bit later.

Remastering now in our distribution is much more functional that gives live-tools Debian.

Actual (in my opinion) lead to conform libraries Light-Debian and Porteus-Wheezy. But it is difficult and laborious work.

Sergey.

[fredx181]

https://drive.google.com/file/d/0ByBgCD ... sp=sharing

Thank you, Fred.
I will include them in the 021-apps-porteus.xzm

Thanks Toni
Can you also test with the EXIT option?
About what you said using 3 modules the system is more stressed, i noticed also that memory usage is a lot higher than the previous light-wheezy with 1 module.
It's nice option to have all in one iso but maybe it's better to separate them in 2 iso's

Fred

[saintless]

Hi, Sergey

But now we have gone too far (and successfully), to go back.

Yes, I agree. But we can learn some things from there and share what we have here.

(I see that in the Light-Debian now live-boot version 3.0.23.1 but I missed something, and I continue to refer to it as 2.0.15, sorry).

Just to remind for everyone who is interested:
DebianDog is pure Debian Wheezy build and has the original live-boot v.3.0.23.1 + some manual added files from live-boot v.2 to make sfs-tools from Russian sfs puppy work on DebianDog.
You can boot DebianDog with the original kernel made with live-boot-initramfs-tools v.3. It is uploaded on the site.
The initrd.img (486 and 686) we use in DebianDog as default are made with downgraded live-boot version of DebianDog. I used this downgraded live-boot DebianDog version only to build the initrd.img files and then I deleted this version.
I'm sure Cat-0.2.iso also will boot with initrd1.img from DebianDog and will have /live/cow and /live/image back.

I enjoy the work of Fred in which he successfully integrated capabilities Porteus and do not hurt Debian.

Yes, I'm glad Fred has found this thread

Remastering now in our distribution is much more functional that gives live-tools Debian.

I'm afraid this is the only option we have. The changes and fixes are so many and we can not reproduce them in the exact order from fresh start.

Toni

[saintless]

Can you also test with the EXIT option?
About what you said using 3 modules the system is more stressed, i noticed also that memory usage is a lot higher than the previous light-wheezy with 1 module.
It's nice option to have all in one iso but maybe it's better to separate them in 2 iso's

Hi, Fred.
I will test the EXIT option.
I also noticed more memory usage with 3 modules.
Till we have DebianDog Beta I will continue updating only one testing squashfs module with 2 kernels included like 01-v3.squashfs
Maybe the idea to separate kernels not worth high ram and cpu usage. I also start to think separate version for each kernel with only one module is the best option. But we have time to decide this later.
I already have separate kernel modules and I will upload them anyway as option.

Toni

[sklimkin]

Hi All!

Install keyboard switcher for XFCE (I will not ship you this question):
# apt-get update
# apt-get install xxkb - 221 KB of disk space
# apt-get install xfce4-xkb-plugin - 3198 KB of disk space
# apt-get clean

Sergey.