Lupu-515 Beta New Version DEC 18

[playdayz]

In a matter of seconds the mymusicsfs-1.sfs will appear in your /mymusicpets directory.
You new sfs is ready to use.

That's exactly what I did with about 30 pets to make ttuuxxx's treasures.

[cthisbear]

" We added it and it seemed there were conflicts "

Can't it be put in the >> drivers SFS.

What I'm saying is if you have no phone line,
and only a wireless connection....you're done.

And with Firesheep around - am I going to lower the bar??

Also some thought has go into adding those crappy Atheros drivers
as well.

That's where I'm coming from.

Chris.

[playdayz]

What I'm saying is if you have no phone line,
and only a wireless connection....you're done.

Clarify for me if you could, please. I thought you could get online without pwireless2 but without the level of encryption you wanted. Is that wrong, and you can not get on line at all without pwireless2? Thanks.

Also if you could link to the drivers I will put them in PPM. I know you might have already, and I am *almost* keeping up. Thanks.

[playdayz]

Someone asked about what Xorg_High did. It provides the glx drivers to allow hardware direct rendering. It provides the drivers for a number of different cards--basically all of the cards. The nv driver doesn't work very well with these drivers which is why we recommend the nvidia pets. The HD2400-5900 ATI Radeon cards perform much better, about twice as well, with their proprietary ATI Catalyst driver, which is what we recommend for them. Everything thing else including Intel cards, etc., can use Xorg_High for reasonably good performance. The ATI Radeon cards also work reasonably well with Xorg_High for those who want to stay open source.

[01micko]

I've an idea...

Maybe we can hide the pwireless2 pet some where in the iso and have a menu entry to activate the install of the pet..

Cheers

[playdayz]

I've an idea...

Maybe we can hide the pwireless2 pet some where in the iso and have a menu entry to activate the install of the pet..

Possible, but do you remember when we put it in and what the results were? I *think* I remember there was a problem and we (or I) thought that Pwireless2 might be the culprit, but I did not do exhaustive testing. Maybe we should try again. There is no dispute that it is a good program.

[shinobar]

I keep having the impression, that National Language Support is the poor guy in puppy.

You are right. It has long history, and we are still on the halfway.

If the main sfs is NLS ready, we can take the strategy:
(main sfs) + (adddional NLS pet or sfs)

But the main sfs is not NLS ready, we need to replace something in the main sfs.
(main sfs) + (replace the components to be NLS ready) + (adddional NLS pet or sfs)

The yaf-splash in woof used be not supporting UTF-8, but now it is replaced by the UTF-8 supporting one.
But still some dialogs in the woof do not support UTF-8.
At least 'dialog' and 'xmessage' in the woof do not support UTF-8.

I am not sure the status of the each Puppy,
but as for the LupQ has 'dialog' with UTF-8 support and replaced 'xmessage' by 'gxmessage'.
EDIT: fluppy-008 also replaces 'xmessage' by 'gxmessage'. I remember Puppy- 4.2.x did so.

[bigpup]

From Barry's blog about UTF-8. Not sure if this means anything concerning the discussion.
http://bkhome.org/blog/?viewDetailed=01977

[shinobar]

Replacing PETs to SFS is nice.
But there are 2 problems.
One is how to do it for SFS the pinstall.sh/puninstall.sh in PETs.
Another is how to deal with the confliction of files with that of main sfs.

If a file exists both in a PET and the main sfs, the one from the PET overwrites the one of the main sfs.
But the file in a SFS, it does not overwrite the main sfs.

There are SFSs, Nvidia-256.35-k2.6.33.2.sfs, and ffmpeg-0.6-lupq-1.sfs, both for LupQ.
They do not work on Lupu/Luci because some files conflict with the main sfs. (Compatibilities)
The additional SFS can overwrite the main sfs as for LupQ, but most of Puppy/woof do not.
See the Puppy-431JP release note

Files on the main SFS can be overridden by extra SFS files same as PET packages do.

BTW, the rule to find out the main sfs is much modified in the recent woof, and it does strange behavior, i think it a bug.

[ttuuxxx]

ttuuxxx, You made that Ogle look good enough and small enough that it would be possible to include in the iso. *Except* the full screen does not work in Openbox. It does work in jwm--my guess is because they both use some older method. Is there any chance you can get the full screen to work in Openbox? Or maybe someone knows what I am doing wrong.

hmmm you need to add /root/.config/openbox/rc.xml the following code to the keybindings section So I you click Alt F11 it will go to fullscreen. first restartX to test changes, It doesn't expand the picture but it gives it a black background and removes the window dressings.
Ps Alt F11 is the default fullscreen on JWM


<keybind key="A-F11">
<action name="ToggleFullscreen"/>
</keybind>


ttuuxxx

[shinobar]

Puzzling

I have samba share on my home LAN. The samba server is on Vine Linux and the shared folder is public, any user can full access without password.

The Lucu/LupQ-511 had same problem.
Connect the remote public share folder using Pnethood. When i click a video file in the remote folder, Gnome-mplayer plays back the remote video file.
When i click a text file in the remote folder, Geany launches but the Geany cannot load the text file.
Unmount the remote folder, then re-mount the same folder, then the problem disappears. Geany can now open the remote text file.
EDIT: Not sure. some time Geany can open the remote text file and some time not.
Puzzling...

I tested the Luci-241 because it has the new version of Pnethood.
The problem in the Lucu/LupQ-511 disappeard!
Geany can open the remote text file from the first mount.

But another new trouble in Luci-241...
When i copy a file to the remote folder, an error occurs:

Copying /mnt/sda3/tmp/some.txt as /mnt/network/SHINOBAR/video/public/tmp/some.txt
cp: failed to preserve ownership for `/mnt/network/SHINOBAR/video/public/tmp/some.txt': Permission denied
Failed to copy '/mnt/sda3/tmp/some.txt'

Actually, the file is copied successfully. The problem is only the error message.

I saw the mount command:
Luci-241 shows,
//192.168.11.2/video on /mnt/network/SHINOBAR/video type cifs (rw,mand,relatime,unc=\192.168.11.2\video,username=guest,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.11.2,serverino,acl,rsize=16384,wsize=57344)

LupQ-511 shows,
//192.168.11.2/video on /mnt/network/SHINOBAR/video type cifs (rw,mand,relatime,unc=\192.168.11.2\video,username=root,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.11.2,file_mode=0755,dir_mode=0755,serverino,rsize=16384,wsize=57344)

The deference must come from the Pnethood verson.
EDIT: It is sure. I replaced whole /usr/local/apps/pnethood directory on the Luci-241 with that of LupQ-511, and confirm the mount command shows the same as LupQ-511 and copy with no error message.
But i cannot find what is the deference in the mount options between 2 versions of pnethood.

EDIT: Luci-241(pnethood-0.6.6) issues next mount command:
mount-FULL -t cifs //192.168.11.2/video /mnt/network/SHINOBAR/video -o servernetbiosname=SHINOBAR,username=guest,password=guest,iocharset=utf8
LupQ-511(pnethood-0.65i18n1) issues:
mount-FULL -t cifs //192.168.11.2/video /mnt/network/SHINOBAR/video -o servernetbiosname=SHINOBAR,guest,iocharset=utf8
But the problem seems not there.

...

[Tasgarth]

Luci 241
Testing 'move' and 'copy'

Move :
--- From NTFS file to ext3 : OK

--- From ext3 file to NTFS :

Operation not supported
Failed to move /root/monfichier.txt as /mnt/sda8/monfichier.txt

Done
There was one error.

But.... it's OK
----------------------------------------------------------
Copy:
--- From NTFS file to ext3 : OK
--- From ext3 file to NTFS :

Operation not supported
Failed to copy /root/monfichier.txt as /mnt/sda8/monfichier.txt
Done
There was one error.

But it's OK
---------------------------------------------------------
--- Move from sda1 (ext3) to sda5 (ext3): OK
--- Copy from sda5 (ext3) to sda1 (ext3): OK

--------------------------------------------------------
--- Move from sda1 (ext3) to sda5 (ext4): OK
--- Copy from sda5 (ext4) to sda1 (ext3): OK

[shinobar]

Luci 241 Testing 'move' and 'copy'

Confirmed. Same as the remote shared folder.

Copying /root/my-documents/tmp/README-tmp.txt as /mnt/sda1/tmp/README-tmp.txt
cp: preserving permissions for `/mnt/sda1/tmp/README-tmp.txt': Operation not supported
Failed to copy '/root/my-documents/tmp/README-tmp.txt'

(Actually coppied.)

Code: Select all

/dev/sda1 on /mnt/sda1 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,blksize=4096)

EDIT: Tested Qirky-140 and it does not show any errors.
Seems not the woof thing. the version of ntfs-3g?

[Béèm]

I keep having the impression, that National Language Support is the poor guy in puppy.

You are right. It has long history, and we are still on the halfway.

If the main sfs is NLS ready, we can take the strategy:
(main sfs) + (adddional NLS pet or sfs)

But the main sfs is not NLS ready, we need to replace something in the main sfs.
(main sfs) + (replace the components to be NLS ready) + (adddional NLS pet or sfs)

The yaf-splash in woof used be not supporting UTF-8, but now it is replaced by the UTF-8 supporting one.
But still some dialogs in the woof do not support UTF-8.
At least 'dialog' and 'xmessage' in the woof do not support UTF-8.

I am not sure the status of the each Puppy,
but as for the LupQ has 'dialog' with UTF-8 support and replaced 'xmessage' by 'gxmessage'.
EDIT: fluppy-008 also replaces 'xmessage' by 'gxmessage'. I remember Puppy- 4.2.x did so.

Thank you for confirming my 'guts' feeling was right.
As long as there is awareness and progress for supporting NLS, it is ok.
I don't know how I can contribute, but all I can do for the moment is informing about an issue in this domain.

And yes, Jemimah confirmed that xmessage is a symlink to gxmessage.
I asked her confirmation if gxmessage fully supports my NLS configuration. I'll report back on this.

If this issue has to be taken to another forum, like the localization project, I can do it, but I fear having less attention and advice from the community.
What do you think?

[shinobar]

And yes, Jemimah confirmed that xmessage is a symlink to gxmessage.
I asked her confirmation if gxmessage fully supports my NLS configuration.

I am not sure but i do not like the gxmessage. I hope someone make an alternative using gtkdialog.

If this issue has to be taken to another forum, like the localization project, I can do it, but I fear having less attention and advice from the community.
What do you think?

I guess the readers here are interested in NLS and what is 'NLS ready' i say, no?

[Béèm]

FBPanel behavior.
Not necessarily a 240 issue.

When the system tray is at the bottom, a maximized program doesn't cover the tray.

As I like the tray at the left-side horizontally, I configured FBpanel so.
But the tray covers a maximized application. And some menu options can't be clicked then.

So I thought I was clever in making the tray hide, unless the mouse hovers over it.
But that doesn't work equally, as when the mouse is near the tray position (I would say if the mouse is 1 1/2 times the width of the tray), so still inside the application window, the tray pops-up, preventing equally to select menu items again.

I looked at the options for FBpanel, but fail to see that I can change the configuration to avoid this situation.

The only solution I see is, that the tray pops-up when the cursor hits the edge of the screen.
I don't know if it is possible to implement this.

[Béèm]

What do you think?

I guess the readers here are interested in NLS and what is 'NLS ready' i say, no?

Well that was my opinion also to continue to post here.
So I'll continue to raise the 'issue' here.

[Béèm]

ABIword with a picture (logo)
Mostly the first thing I do in a fresh install (like here in 240) is to set open with to soffice, so I can open a .doc in OOo.
This time I forgot and clicking on a .doc opened it with ABIword.
The first thing in the doc is a picture (logo), but it did display as a compressed line.
Opening the .doc with OOo, the logo was displayed correctly.

I don't know if this issue with ABIword is new in the 240 or if it already was there before.
Altho I don't use ABIword, I thought it was good to report.

[scruffy]

FBPanel behavior.
Not necessarily a 240 issue.

When the system tray is at the bottom, a maximized program doesn't cover the tray.

As I like the tray at the left-side horizontally, I configured FBpanel so.
But the tray covers a maximized application. And some menu options can't be clicked then.

.

1)Check size of panel in pixels using extra configuration options
<ctrl> <right click> on panel.
2)Reserve leftmost portion of screen for FBpanel
Menu option Desktop>Desktop settings>Openbox Window manager config>Margins
Set the left margin to appropriate number of pixels.

Hope that works.

[DaveS]

Could somebody take a quick look at this and comment please http://www.murga-linux.com/puppy/viewtopic.php?t=62611