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

[saintless]

Hi, Fred.
Take your time. I just share what I see as potential problems from testing.

Btw, how you define "logout and login back in" ? Exit X and startx doesn't do that, I think.

With XDM activated even Ctrl+Alt+BackSpase drops out to login prompt.
Without XDM -> Shutdown -> Exit WM:

Code: Select all

exit
login
puppy
puppy
startx

...honestly I'm confused about how these things work.

Me too, Fred, I will do more testing with sudo and gksu and gsu. I remeber I had troubles with permissions in Jwm version with ktsuss-gsu but I will test it again.

Standard Debian Gnome asks for password only first time starting gksu if I do not mistake. Then it does not ask for password anymore.
I know in the same terminal sudo does not ask for password second time. This why I wrote it might be not gsu problem.
Still I do not like surprises like removing by accident user from group wheel just because for some reason password prompt is not active. Atleast I like to know why this happens.
We have much work to do for the next version, but lets keep it for later - after New Year.

Toni

[fredx181]

Hi Toni,

Take your time. I just share what I see as potential problems from testing.

Yes, and thanks for testing.
I see it as my responsibility because I like to include the graphical sudo

Still I do not like surprises like removing by accident user from group wheel just because for some reason password prompt is not active. Atleast I like to know why this happens.

I assume you refer to this you wrote earlier:

First run I use Cancel button on gsu window and get this message on the attached picture: "Puppy user added to group wheel." But it is not added:

I found the reason for it is mistake in gsu script, on line 28 instead of:

Code: Select all

[[ $ret -ne 0 ]] && exit 0

It should be:

Code: Select all

[[ $ret -ne 0 ]] && exit 1

The shutdown-pass-activate_deactivate script gets $ret value from it, that's why it gives message 'succeeded' (exit 0), when canceled it should read $ret value as 1 (exit 1)

Attached new gsu with correction and:
"gsu-notimeout" from which I deleted the "check for sudo" part and also added "sudo -K" command (it should disable timeout for password, so this way every time entering password is required).
I see the "timeout" for password as a feature which is enabled by default for some time (still don't know how long, I read different things about it on documentation on the net, if it's 5 minutes or 15 minutes, didn't yet have the patience to test )
Or maybe it is valid for the whole login session.

Fred

[saintless]

Thanks, Fred

I confirm it is working and I vote for gsu-notimeout as default.
We can include both in gsu package if you like:
gsu (renamed from gsu-notimeout)
gsu-timeout (or other name for the other gsu).
Then the user can easy switch the names in /opt/bin if needed without having troubles to uninstall/reinstall gsu package later.

From what I read gksu, gsudo, ktsuss should be used inside /usr/share/application desktop files or /usr/share/menu if the user decides to run applications as root or to skip typing sudo in terminal for programs in /sbin, /usr/sbin. And I think most of the posts describe this as not recommended.

I think the packages in debian repository are made by default for multiuser use and the solution they use is not sudo or gksu, but the program write only in $HOME/ and it is started from PATH available as default for user account (like /usr/bin, /usre/local/bin, /bin).

In DebianDog we use different method from the start adding gsu line for almost every script.
William for example makes the packages work without gsu line (ffconvert, precord, pavrecord, domyfile, domycommand).
I don't say to skip gsu line inside scripts in the future, but we can hope the user will use them careful after having password prompt every time starting the program.
For example latest apt2sfs can easy break the system without reading how to use it properly. If I cancel the proces installing packages in the middle or after, I have few seconds interval before the message "Trying to recover dpkg databse" appears. I can easy reboot or logout for these few seconds or just to ignore the message and reboot. Or maybe pawer failure could happen. Then status file is broken.
The first apt2sfs without installing packages or the later (without copying status from main module) were not smart, but safe.
All I mean is we should have password prompt every time gsu script is called hoping this will make the user more careful with scripts containing gsu line.

I hope this makes sense

BTW just for information we have available different GUI with root password prompt (su-to-root -X -c command-name). For example Gparted /usr/share/menu file is started this way by default:

Code: Select all

?package(gparted):\
	needs="X11"\
	section="Applications/System/Administration"\
	title="GNOME partition editor"\
	command="su-to-root -X -c /usr/sbin/gparted"\
	icon="/usr/share/pixmaps/gparted.xpm"

Picture attached.

Happy Holidays!

[fredx181]

Hi Toni,

We can include both in gsu package if you like:
gsu (renamed from gsu-notimeout)
gsu-timeout (or other name for the other gsu).
Then the user can easy switch the names in /opt/bin if needed without having troubles to uninstall/reinstall gsu package later.

Yes, it's fine by me this way.

.....
.....
I hope this makes sense Smile

It surely does.

BTW just for information we have available different GUI with root password prompt (su-to-root -X -c command-name). For example Gparted /usr/share/menu file is started this way by default:

The GUI you see is just the same as ktsuss.
The su-to-root script checks for 'which ktsuss' and use it if any other (like gksu or kdesu) is not available

Happy Holidays!

Thanks, same to you Toni!

[fredx181]

Hi All,

Here's a script using yad that does a similar thing as gtkdialog-splash. (It's much more simple though)
.
Started this to make it possible to show a nicer colored splash message in scripts that use yad as frontend.
(don't like mixing it with gtkdialog-splash)
All yad parameters can be used plus a few additions (foreground, background, fontname)
For usage type: yad-splash --help

Some examples: (see also pictures)
Example1:

Code: Select all

./yad-splash --image browser-dload --image-on-top --bg '#F4E48F' --text "  Downloading...  " --undecorated --no-buttons &

Example2:

Code: Select all

./yad-splash --borders 5  --text "    Virus detected! \n Name is: Window$  \n \n    Remove it?" --fontname "Bold 18" --bg "dark red" --fg "yellow" --undecorated --button="gtk-yes:0" &

Attached: yad-splash.tar.gz

Edit: To show what's more possible here's another example (more complicated, using <span ...>)
Example3:

Code: Select all

./yad-splash --borders 5  --text "<span size='large' foreground='#432424'><b> All updates are done.  </b></span> \n <span foreground='dark red'><b> A reboot is required. \n      Reboot now?  </b></span>" --bg '#F4E48F' --fg '#7B2365' --undecorated &

This makes the buttons font different color as the text.

Fred

[saintless]

Hi, Fred.

Here's a script using yad that does a similar thing as gtkdialog-splash. (It's much more simple though)

Added in next version changes post. I guess you are going to use it for yad scripts in the future.
If you like to have new scripts containing yad-splash compatible with different Debian I can make deb package (location /usr/local/bin/yad-splash) and add yad as dependency inside control.

Some changes in the testing repository:

Terry's mk-jwm.menu added as mkjwmmenu_1.0.0-1_i386.deb containing Menu-Puppy and Menu-Debian setup.
MJWM added as /mjwm_4.0.0-1_i386.deb with dependency mkjwmmenu (because it will use auto-update menus scripts from there).
Both packages work with standard Debian if JWM is started. Menu-Debian and Menu-MJWM work with dash. Only Menu-Puppy (mk-jwm.menu) needs bash reconfiguration.

Added extra category in some packages desktop file to make them appear in the right place for menu-MJWM.

x11-xserver-utils and xdm packages - dependency cpp was removed from both. I don't like to keep it removed since we are making DebianDog packages compatible with standard Debian. Now cpp is added as Recommends: in control and will not be installed in DebianDog. But cpp will be installed in standard Debian where recommended packages are auto-installed. This means if both packages are upgraded in standard Debian cpp will be kept as it should without creating troubles.

RemasterCow with .wh support needs a button or other way to provide information explaining properly what whitout function means and how to use it properly (only with enabled dpkg registration).

We need to decide what to do with (15. export LC_ALL=C) from next version changes post. Just post with information about this problem or to add it in all scripts in the future?

But all this can wait till next year

Edit: BTW found one situation when apt2sfs will fail creating broken module. Using with save file if there is no space left the instalation process fails (reading the messages in terminal), but apt2sfs continue with copying in work folder, uninstalling packages and creating new module. This may happen often for someone using small save file like me (300 - 1000Mb).
I think dpkg checks if there is enough free space only for downloading the packages and not if there is enough space to extract them after that.
Maybe we can add this information in apt2sfs window with bold or red text?

Toni

[fredx181]

Hi Toni,

Added in next version changes post. I guess you are going to use it for yad scripts in the future.
If you like to have new scripts containing yad-splash compatible with different Debian I can make deb package (location /usr/local/bin/yad-splash) and add yad as dependency inside control.

Yes, that would be good, it may be useful sometimes for new scripts.

Some changes in the testing repository:
....
....

Seems like you made improvement!

RemasterCow with .wh support needs a button or other way to provide information explaining properly what whitout function means and how to use it properly (only with enabled dpkg registration).

Ok, I recently found out that yad supports also a "normal" button (instead of the sort of hidden button used in Remastercow for showing info about dpkg registration)

Two ways:
Create file with the info inside (and make it read-only), then it could be like this with added "Information" button to Remastercow:
(as example used /opt/docs/welcome using leafpad, can be changed maybe to 'default_editor')

Code: Select all

yad --title "Info-button-example" --borders 5 --text "Example for button opening text file for info" --button "gtk-info:leafpad /opt/docs/welcome" --button "gtk-quit:1" --button "gtk-ok:0"

Or like this using yad text-info

Code: Select all

yad --title "Info-button-example" --borders 5 --text "Example for button showing info." --button "gtk-info:sh -c "'"'"echo -e 'Information... \nMore information on new line. \nEven more information on new line' | yad --title "Information" --margins 5 --text-info --width 500 --height 400 --wrap"'"'"" --button "gtk-cancel:1" --button "gtk-ok:0"

You choose!
If you prefer the latter you could pass me the text (next year ) and I'll add it to the script.
Same thing for apt2sfs maybe?

Edit:

We need to decide what to do with (15. export LC_ALL=C) from next version changes post. Just post with information about this problem or to add it in all scripts in the future?

Not add it to all scripts in the future, only when needed.
It's only a problem for some scripts, specially the ones with some grep commandline that checks for output text (which isn't always english when locale has been changed)
I will test more scripts for any issues.

Fred

[saintless]

Thanks, Fred!
I will test both button options but for RemasterCow I think it is best to have the same as for dpkg registration.
Button with title "Information" could be easy ignored. I'm testing button just below whiteout check box with title "Click here for more info about whiteout files". I will upload it after the holidays for final check and decision from you.

About apt2sfs I need some more time to test how dpkg checks for free space before installing packages. It is more likely the checking is for free space to extract the packages but it doesn't calculate inside the space needed for downloaded deb files.
The latest apt2sfs has disadvantage in such situation compared to the older apt2sfs. Even if the user can see the error messages for not enough space in terminal window we need to make sure apt2sfs will not be closed without restoring status file. The information must be visible on first run at least and well explained. Maybe we can use first time run message that apt2sfs already has to recommend clicking the "Information" button before using the program. We will discuss this when I have something for testing.

Merry Christmas!

[fredx181]

Hi Toni,

About apt2sfs I need some more time to test how dpkg checks for free space before installing packages. It is more likely the checking is for free space to extract the packages but it doesn't calculate inside the space needed for downloaded deb files.
The latest apt2sfs has disadvantage in such situation compared to the older apt2sfs. Even if the user can see the error messages for not enough space in terminal window we need to make sure apt2sfs will not be closed without restoring status file. The information must be visible on first run at least and well explained. Maybe we can use first time run message that apt2sfs already has to recommend clicking the "Information" button before using the program. We will discuss this when I have something for testing.

Thanks for noticing this issue with apt2sfs.
I decided the best to do is improve error checking for apt2sfs.
I think one of the most important things for a script is error checking (and btw, one of the most difficult things) so that the user isn't confronted with any surprises.

It checks now for any dpkg error (on line 388-397 that depends on added lines 336-339) and if there is, it shows clear message with last log lines in bold (from /tmp/aptout) and in red font a message informing about "No space left on device" and the possible reason (to small savefile or not enough RAM)
In this error case the module will not be created and the system will be restored.
(I think no info button will be needed this way)

Test it whenever you like, no hurry at all.

Attached new apt2sfs.tar.gz (finished it just before Christmas )

Btw, for me Christmas doesn't mean much to me (I'm not religious), I have dinner appointment tomorrow and that's it, live goes on as usual except that around me some things are stopped, so I'm sort of forced to have holiday, which is Ok .

Fred

[saintless]

Much better this way, Fred, thank you!



In next version changes post apt2sfs linked to this new version.

Edit: And testing RemasterCow with whiteout files info button. Still not sure if it is clearly explained.

Edit2: Fred, for next update remove /opt/bin/cow-nosave, cow-save-part, cow-save-file. I will add it to the changes post. After we use as default your cowsave the old scripts could become dangerous if started by accident. They depend on the boot method to work properly.

Edit3: Flashplayerchoice does not work for me with yad-gsu (timeout or notimeout), Fred. Tested only as user in Jwm version but I think it will be good to include gsu-xterm in gsu.deb and use it in such situations. I will test later how to fix flashplayerchoice or the menu files to work with yad-gsu. We will need much testing before next update.

Edit4: Same with Change frisbee with sns script. Doesn't work with gsu-yad. I can include gsu-xterm in gsu-deb and change the lines for scripts with this problem to gsu-xterm. But this will break the same scripts after installing the gsu.deb on older DD version. This gsu change gets too complicated and I'm sure I will miss something that does not work after changing gsu-xterm in Jwm version.
What do you think, Fred? Any idea how to keep compatibility with old DD versions and using gsu-yad. I don't like the idea to edit the scripts for yad-gsu because for older DD versions will need reinstalling/replacing all moded to work with gsu-yad scripts after installing gsu.deb. And installing new gsu.deb will be needed to make shutdown without password work on old DD. I think the safe way is to include in gsu.deb gsu-xterm as default /opt/bin/gsu.

Toni

[fredx181]

Hi Toni,

Much better this way, Fred, thank you!

Glad you like new apt2sfs error checking solution!

Edit: And testing RemasterCow with whiteout files info button. Still not sure if it is clearly explained.

Although it's hard to imagine to know nothing about it, I think it's very well explained. Thanks!

Edit2: Fred, for next update remove /opt/bin/cow-nosave, cow-save-part, cow-save-file.

Yes, good decision.

Edit3: Flashplayerchoice does not work for me with yad-gsu (timeout or notimeout),
......
......
Edit4
.....
I think the safe way is to include in gsu.deb gsu-xterm as default /opt/bin/gsu.

I would agree if there isn't a simple solution.
This is about terminal-scripts only I think, and there are just a few, why not edit them?
For example for flashplayerchoice there are 2 ways AFAIK:
- Edit Exec= line in /usr/share/applications/flashplayerchoice.desktop to:

Code: Select all

Exec=gsu xterm -e /opt/bin/flashplayerchoice

Then delete gsu line in /opt/bin/flashplayerchoice?
or:
- Change gsu line in flashplayerchoice script (or any other terminal script) to;

Code: Select all

[ "`whoami`" != "root" ] && exec gsu xterm -e ${0}

Then Exec= line in /usr/share/applications/flashplayerchoice.desktop could be without xterm:

Code: Select all

Exec=/opt/bin/flashplayerchoice

I think the last option is best (in case flashplayerchoice is run from terminal)

Edit:

I don't like the idea to edit the scripts for yad-gsu because for older DD versions will need reinstalling/replacing all moded to work with gsu-yad scripts after installing gsu.deb.

Sorry, didn't read above well enough about compatibility with older versions, well... I don't know yet what's good solution.

Fred

[saintless]

I would agree if there isn't a simple solution.
This is about terminal-scripts only I think, and there are just a few, why not edit them?
For example for flashplayerchoice there are 2 ways AFAIK:
- Edit Exec= line in /usr/share/applications/flashplayerchoice.desktop to:

Code: Select all

Exec=gsu xterm -e /opt/bin/flashplayerchoice

Then delete gsu line in /opt/bin/flashplayerchoice?
or:
- Change gsu line in flashplayerchoice script (or any other terminal script) to;

Code: Select all

[ "`whoami`" != "root" ] && exec gsu xterm -e ${0}

Then Exec= line in /usr/share/applications/flashplayerchoice.desktop could be without xterm:

Code: Select all

Exec=/opt/bin/flashplayerchoice

I think the last option is best (in case flashplayerchoice is run from terminal)

Edit:

I don't like the idea to edit the scripts for yad-gsu because for older DD versions will need reinstalling/replacing all moded to work with gsu-yad scripts after installing gsu.deb.

Sorry, didn't read above well enough about compatibility with older versions, well... I don't know yet what's good solution.

Hi, Fred.

Sorry I didn't explain this well enough. Your suggestion for editing scripts in desktop file or inside the script is fine. We can do it this way.

What I mean is to include in gsu.deb - gsu-xterm, gsu-timeout, gsu-notimeout and link gsu pointing by default to gsu-xterm.
Then if gsu.deb is installed on old DD version it will not break the existing scripts that depend on gsu-xterm.
And for next update we will install the same gsu.deb but changing manually gsu link to point gsu-notimeout and editing scripts like flashplayerchoice.
Then we get yad-gsu for new version and we keep compatibility with old DD versions after installing new gsu.deb because it will use gsu-xterm by default. And if gsu.deb is reinstalled on next DD update from the user it will still work the same way for all scripts with gsu-xterm and gsu link can be easy changed to gsu-notimeout or gsu-timeout. The point is gsu-xterm as default gsu in deb package will be universal for all DD versions and for different Debian and will not break existing scripts in old DD.

Edit: If you like I can test some way to check in postinst script for DD version and if the new one is found then gsu link will be changed to point gsu-notimeout. Maybe if we add special file in next DD updates it can be used from postinst script to change the gsu link for new DD versions.

Edit2: For Jwm version I will need to combine both solutions. Unfortunately mk-jwm.menu and mjwm do not read Terminal=true/false in desktop files. If "xterm -e" is missing, then the program does not start from menu as root. Debian menu does not have this problem. Setting up in /usr/share/menu needs=text/x11 works to start terminal without having "xterm -e". move-in-crypt for example needs "xterm -e" in desktop file for root and at the same time gsu line changed to "exec gsu xterm -e" for user.

Edit3: Fred, if you agree about gsu deb suggestion here is testing package:
http://smokey01.com/saintless/DebianDog ... 1_i386.deb
gsu is link to gsu-xterm by default. If /opt/docs/debdognew file is found then gsu will be linked to gsu-notimeout.
Attached debdognew in zip archive. Extract it in /opt/docs

Edit:4: Can you please check out also this obshutdown-porteuswheezy_0.1.1-1_i386.deb, Fred? I tried to make it work out of the box for OpenBox version. For Jwm it will need only small change for Exit X and editing the entry in Jwm and Icewm configuration files, but I keep the changes in 021-apps-porteus anyway. If it works as it is for you I will leave it as official package. The name is obshutdown-porteuswheezy and it is better to keep it, because this is the name in status file in older DD versions.

Toni

[fredx181]

Hi Toni,

What I mean is to include in gsu.deb - gsu-xterm, gsu-timeout, gsu-notimeout and link gsu pointing by default to gsu-xterm.
.....
.....

I see now, did misunderstand.

Edit3: Fred, if you agree about gsu deb suggestion here is testing package:
http://smokey01.com/saintless/DebianDog ... 1_i386.deb

Yes, Ok for me and it works, very smart way!

Edit:4: Can you please check out also this obshutdown-porteuswheezy_0.1.1-1_i386.deb, Fred?

I will check later.
Yes better keep it same name.

A wild experiment :
I stripped down gksu package a lot (uncompressed 813K)
(Added dependency libraries and files to it)
Named it gsu so it will replace existing gsu package and /opt/bin/gsu script which executes gksu sudo-mode.
Tested only on Openbox version with this 'sudo-mode', works well and no errors are shown in terminal (using plain gksu displays a warning, btw).
It needs more work though to make it not conflict with other packages.
Just for testing another small graphical sudo choice besides gsu-yad.
I like it, if you do also I will put more effort in this to make it compatible with DD and standard Debian.
(don't know how yet, perhaps use /opt/lib or/and add some more dependencies than it is now in control file.)

gsu_2.0.2-6_i386.deb:
https://googledrive.com/host/0ByBgCDlZZ ... 6_i386.deb

Fred

[fredx181]

Double post accidentally, removed.
Fred

[saintless]

A wild experiment :
I stripped down gksu package a lot (uncompressed 813K)
(Added dependency libraries and files to it)
Named it gsu so it will replace existing gsu package and /opt/bin/gsu script which executes gksu sudo-mode.
Tested only on Openbox version with this 'sudo-mode', works well and no errors are shown in terminal (using plain gksu displays a warning, btw).
It needs more work though to make it not conflict with other packages.
Just for testing another small graphical sudo choice besides gsu-yad.
I like it, if you do also I will put more effort in this to make it compatible with DD and standard Debian.
(don't know how yet, perhaps use /opt/lib or/and add some more dependencies than it is now in control file.)

gsu_2.0.2-6_i386.deb:
https://googledrive.com/host/0ByBgCDlZZ ... 6_i386.deb

Fred

Hi, Fred.
Thanks, it works form quick testing in Jwm version but I like yad-gsu-notimeout more. I guess the libs are official wheezy and some will stay hidden for dpkg + the complications to prevent conflicts with official gksu files make gsu-yad better choice for DebianDog in my opinion.
If you still like to work on this and include it as extra package I suggest (if it is possible) to keep all dependencies included inside control by moving all you stripped down from Depends: to Recommends: This is what I did atlast with xdm and x11-xserver-utils and makes the packages small for DebianDog and basicly without changes for standard Debian, because reocommended packages are auto-installed.

BTW the testing I made is comparing all gsu packages (all ktsuss, all gsu versions, gsudo and this last gksu from you, su-to-root and sudo) with RemasterCow from user account in Jwm version. I have RemasterCow and RemasterDog and PureFtpd started with /opt/bin/gksu-root which starts /usr/bin/ktsuss.
The result is only ktsuss does the cleaning from $HOME/.local properly. In openBox and Jwm ktsuss is different but works the same way.
RemasterCow started with any other script (gsu, gksu, /opt/bin/ktsuss2, gsudo, sudo, su-to-root) from user account Puppy cleans files in /root/.local instead $HOME/.local (or /home/puppy/,local).
Haven't tested this in OpenBox version so it may be different there. I remember I had some PATH problem for su-to-root after installing xdm in Jwm version and maybe this is the reason but I will keep ktsuss for RemasterCow, RemasterDog and PureFtpd for user account.

Toni

[fredx181]

Hi Toni,

Thanks, it works form quick testing in Jwm version but I like yad-gsu-notimeout more. I guess the libs are official wheezy and some will stay hidden for dpkg + the complications to prevent conflicts with official gksu files make gsu-yad better choice for DebianDog in my opinion.
.....

Yes, ok, I'll see later if I perhaps make extra package from it (indeed it won't be easy at all).

I have RemasterCow and RemasterDog and PureFtpd started with /opt/bin/gksu-root which starts /usr/bin/ktsuss.

I'll do it the same in OpenBox version then. (noticed now you have remastercow-start etc.. in Jwm version)
Btw, I guess you know but FYI: the HOME env in gsu-yad can be easily changed to the user HOME by adding the -E option to the sudo commands.

Here's a script that checks if you are running out of space.
I think it can be useful addition to DD.
Copied info from top of script:

Code: Select all

# Shows gtkdialog-splash red colored warning in that case, it disappears only when space left has been increased again (displays for a short time a green colored message then)
# When space left is low again, it displays again the warning... and so on...
# Needs to run constantly in the background (best to be started at login e.g. put it in  ~/Startup) 

# Set the variable for number of MB space left, there'll be warning if it's less (what is a good amount?)
MBLEFT=15

As you can see above the variable for crossing the line can be changed e.g. MBLEFT=10 and the warning will show only when free space is below 10M.
I found out by testing btw that when free space gets 0, dpkg will be broken (which shouldn't happen IMHO)
Did some attempts to make it run as a daemon by using initscript or from /etc/profile.d but it didn't work out well.
Putting it in ~/Startup works fine.

Any suggestions for improvement are welcome.

Attached freechk.tar.gz

Fred

[fredx181]

Hi Toni,

I made some changes to obshutdown-porteuswheezy_0.1.1-1_i386.deb
- Included the new save2flash
- new snapmergepuppy with a small fix and cleaned it up (there was a lot of unneeded puppy-only stuff inside)
- added dependencies yad and gsu | gksu in control file
- removed Conflicts and Replaces lines for xfce4-session in control file (I think it's solved already by changing name to logout.desktop in /usr/share/applications

I might be wrong about something, just tell me then.

Can you put new save2flash and snapmergepuppy also in 021-apps-porteus.squashfs?

https://googledrive.com/host/0ByBgCDlZZ ... 1_i386.deb

Fred

[saintless]

Hi, Fred.

I'll do it the same in OpenBox version then. (noticed now you have remastercow-start etc.. in Jwm version)
Btw, I guess you know but FYI: the HOME env in gsu-yad can be easily changed to the user HOME by adding the -E option to the sudo commands.

Thanks, I read this in sudo man page but for RemasterCow and RemasterDog I feel like root password is better solution for miltiuser system. Anyway to use "sudo -E" we have to make extra script to start this command instead /opt/bin/gsu-root and we have too many gsu alternatives already.

Here's a script that checks if you are running out of space.
I think it can be useful addition to DD.

Great, thank you! Tested with encrypted persistence save file (live-boot-3) and works for user and root. Does it work the same for save partition and save folder? I will test it later. My suggestion is to add it for root, puppy and in /etc/skel/Startup and make the warning appear for less than 30 Mb. Installing packages or even Firefox cache can use 15Mb in no time while reading the warning.

I made some changes to obshutdown-porteuswheezy_0.1.1-1_i386.deb

Seems fine to me. Uploaded with some other packages in the testing repository. If we do not find something wrong later the packages here are ready for reinstalling:
http://smokey01.com/saintless/DebianDog ... sting/tmp/
I made also IceWM control center reinstallable + adding the dependencies as deb packages insted libs in /opt/lib. Reinstalling the package will find the dependencies and replace /opt/bin files for icecc with symlinks.

Can you put new save2flash and snapmergepuppy also in 021-apps-porteus.squashfs?

Yes, I will add the information in next version changes post also.

Edit: If you prefer sudo -E for RemasterCow, RemasterDog and PureFtpd I do not mind. We can make one more extra script for sudo -E command.

Edit2: BTW seems by accident in DebianDog-Squeeze I made this console-setup on the picture. See user name, password and Ctrl+Alt+F1 collor. I will try to reproduce it in Jwm-Wheezy. If you like to do the same I will post "dpkg-reconfigure console-setup" steps.




Toni

[fredx181]

Hi Toni,

Anyway to use "sudo -E" we have to make extra script to start this command instead /opt/bin/gsu-root and we have too many gsu alternatives already.

For me it's Ok , not another script needed.

Here's a script that checks if you are running out of space.
I think it can be useful addition to DD.

Great, thank you! Tested with encrypted persistence save file (live-boot-3) and works for user and root. Does it work the same for save partition and save folder? I will test it later. My suggestion is to add it for root, puppy and in /etc/skel/Startup and make the warning appear for less than 30 Mb. Installing packages or even Firefox cache can use 15Mb in no time while reading the warning.

Didn't test yet for save partition and save folder but it should work the same as the script checks for free space in /
I agree, 30 MB will be more safe.

Edit2: BTW seems by accident in DebianDog-Squeeze I made this console-setup on the picture. See user name, password and Ctrl+Alt+F1 collor.

Looks the same as I normally see on openbox version.
Maybe because I did once a setup, in /etc/default/console-setup I have:

Code: Select all

FONTFACE="TerminusBoldVGA"
FONTSIZE="8x16"

Btw here's attached new welcome message with Debian logo in 'one piece' (see picture) (remove dummy .tar extension)

Fred

[saintless]

Thanks for the logo fix, Fred!

Looks the same as I normally see on openbox version.

Not like it is something important but I guess it depends on keyboard type or other hardware then.
Can you confirm you see this on the attached picture before X starts with OpenBox version? Or after ExitX from user account and typing exit and Enter? Because I don't see usernames and password different from other text in OpenBox version on boot.
I get this on the picture after:

Code: Select all

dpkg-reconfigure console-setup -> UTF-8 -> Latin1 and Latin5 western Europe... -> Fixed -> 8x13 

Toni