Page 7 of 8

Re: Porteus-v1_beta-i486 ready for testing

Posted: 27 Apr 2011, 01:50
by francois
@burningbush: Maybe you can try this one from:
http://www.slax.org/forum.php?action=vi ... ostid65067

In the KDE panel, the time indicated by the clock does not change though I have set it according to the adequate time zone and though I have modified the clock time thru the adjust date and time clock device. Here is what I did, from:
http://lists.kde.org/?l=kde-linux&m=113579888606118&w=2

All I had to do was to use the command dcopserver in cli mode and reboot to resolve the issue permanently.

root@slax:~# dcopserver

Re: Porteus-v1_beta-i486 ready for testing

Posted: 01 May 2011, 15:08
by ponce
I prepared some new lxde packages on slackware 13.37

http://ponce.cc/slackware/slackware-13.37/lxde/

substitute the pcmanfm package with this one for not having the warning during use as root
pcmanfm-20110422_3f899d1-i486-1ponce.txz

be aware that the following packages shouldn't be needed anymore (gvfs, that should have no dependencies, is used instead of gnome-vfs)

Code: Select all

gnome-mime-data
ORBit2
GConf
libbonobo
gnome-vfs
also, configuration files in /etc are changed, so I suggest to start from the new ones and customize them accordingly (or something may break ;) ).

:beer:

Re: Porteus-v1_beta-i486 ready for testing

Posted: 01 May 2011, 23:06
by francois
1) @burningbush and others:
If the dcopserver command works for you. I would appreciate to get some explanation. It would be appreciated.

Thanks.

Posted after 5 hours 13 minutes 24 seconds:
2) Is there a way in addition to autoexec=toroot cheatcode, to boot all the way winthin X without giving the password?

Re: Porteus-v1_beta-i486 ready for testing

Posted: 01 May 2011, 23:51
by fanthom
@francois
it's 'toroot' and not 'autoexec=toroot' - please read cheatcodes.txt

Re: Porteus-v1_beta-i486 ready for testing

Posted: 02 May 2011, 02:37
by francois
Thanks, I will do it.

Posted after 1 hour 41 minute 59 seconds:
1) Has the /root /.kde/autostart folder been removed temporarily, or has it been moved somewhere else^ I used to drop scripts in there (including my dual display script).

2) toroot does not seem to function in menu.lst always fresh

Salutations distinguees.

Re: Porteus-v1_beta-i486 ready for testing

Posted: 04 May 2011, 03:03
by wread
@brokenman,
@fanthom,
@Hamza,

I am trying to build a module for Google Earth for Porteus V 1.0 -32 bits. The first approach was to translate the google-earth-4.3.lzm from Slax-6.1.2 to Porteus. It runs, but I get empty boxes instead of fonts; the font control has only "Fixed" font size 10 type latin. In Slax 6.1.2 it hat a variety of fonts, sizes and types.

In Slax-Remix and in Porteus 0.9 there is only one fixed font, too.

Then I have built a module for google-earth-5.1.xzm and get also empty boxes where bigger fonts should come; to make it an exercise, I built the google-earth-6.0.1.xzm with the same results.

Running them with lxde did not help at all, same empty boxes. This last version is a pretty thing, for you can fly over the moon and over mars! I got it from slackyd as txz module for Slackware current, so it should run in Porteus, I thought....

http://www.mediafire.com/?zyu3mji9y0iv88g

All tested in 2 machines; external I have qt-4.6.2 installed; I tried with qt-4.7. without luck. Dependencies (ldd googleearth-bin) are all connected. What else could it be?


Good night!
____________________________________________________________________________________________________
The Porteus community never sleeps!

Posted after 23 hours 49 minutes 26 seconds:
Bad news guys!

I packaged the google-earth-6.0.1 directory to a sq3.lzm module for slax 6.1.2 and you can't believe it, the fonts appear ok.

http://www.mediafire.com/?rc6ycqj0b216lqa

You can test it by yourselves.

Checking the chain links we have kernel>core>xorg>kde or lxde>google-earth.
Porteus has a new kernel, a new kde, but not a new lxde, and I don't know if core and xorg are also new; so the bug is in the kernel or in xorg-if it is new-.

Apparently the fonts that fail are streamed by the google server; when you are not conected, the font control can not open the switch, it is grayed. When connected, the fonts can get through.

Our Porteus is sendig those fonts to /dev/null somehow.

Now I will subscribe myself to the XZM-TEAM! 8)

Cheers!
___________________________________________________________________________________________________
The porteus community never sleeps!

Re: Porteus-v1_beta-i486 ready for testing

Posted: 06 May 2011, 04:37
by Falcony
Possible I found a problem in linuxrc.

I do not detect full nature of it but seems it is the bug

In some circumstances there appear message
"!!ERROR!!\nCouldn't copy /sbin/init file - you need at least 600KB free space inside initrd!!
I suppose it is due of lack RAM as it happens in copy2ram mode but I am not sure

In addition - before this there is several another messages
Cannot read module_name.xpm corrupted download?
Not for all modules but for several.

All modules not corruted. If I boot in other mode(normal) - it is ok

I supporse that it is due not enough space for /union mount

But I am not sure as I need additional time to test it in different PC and different modes

Re: Porteus-v1_beta-i486 ready for testing

Posted: 06 May 2011, 05:29
by fanthom
@Falcony
try the latest version of linuxrc which works perfect with 32bit 1.0-beta and will be shipped with FINAL (no new features - just cleanups):
http://www.4shared.com/file/DJI6J6lG/initrd.html
what's the ram size in failing PC? try 000 + 001 modules at the start.

Re: Porteus-v1_beta-i486 ready for testing

Posted: 06 May 2011, 06:11
by Falcony
The size is 512 RAM
I booted all modules except koffice

An once more - when I boot on this PC from pxe boot in normal boot - I see errors regarding some corrupted modules - but it finally boot to Gui
But when I boot on this PC from pxe boot in copy2ram - I see errors regarding some corrupted modules and error about low space in initrc - and it hold

Tnanks. I'll try this fresh linurcrc from this initrd

But result regarging this will be only after weekend L)
If find time

Re: Porteus-v1_beta-i486 ready for testing

Posted: 06 May 2011, 08:14
by fanthom
@Falcony
please use whole initrd and not just linuxrc from it

@brokenman
1) some small bugs
- xpns-tool has a bug in 'Static IP' a it never saves /etc/rc.d/rc.inet (dhcp section must be commented out during boot)
- there should be info that zzz-pns-configs.xzm is placed in /root/Desktop as guests may be confused
- when i answer NO to "do you want to create xzm...." question then nothing happens and application closes. in cli mode there is a info about copying the files manually to proper places in the system - useful when user is saving changes (changes always overrides xzm modules)

i'm really impressed with this tool :)

2) typo in porteus save.dat manager in help file as it says 'posixvol' while should be 'posixovl'

Re: Porteus-v1_beta-i486 ready for testing

Posted: 07 May 2011, 14:58
by wread
A sweet candy for developers: codeblocks-10.0.5 to be run in Porteus V 1.0. You can download it from this link:

http://www.mediafire.com/?er7ub7ay5d3kr

You must also download wxGTK-2.8.12 from the same link. Put it in modules/CodeBlocks/ and reboot and you are coding like a king!

Enjoy! :D

_______________________________________________________________________________________________________
The Porteus Community never sleeps!

Re: Porteus-v1_beta-i486 ready for testing

Posted: 07 May 2011, 19:48
by brokenman
Fixed rempkg, extpkg to support handling of links. Fixed problems with xpns-tool ... thanks fanthom for grep suggestion.

Wread problem with g-earth could be gtk ... please test in porteus 32bit rc1 which will be out tomorrow. Thanks for codeblocks!

Re: Porteus-v1_beta-i486 ready for testing

Posted: 07 May 2011, 20:52
by francois
1) The toroot cheatcode still does not work for me.
2) I am still looking for the kde autostart folder so to put my dual display script.
3) trying to build modules with right click, build module does build from folder contents.

Any comments on these issues are welcome.

Salutations!

Re: Porteus-v1_beta-i486 ready for testing

Posted: 07 May 2011, 21:11
by Hamza
2) I am still looking for the kde autostart folder so to put my dual display script.
Looks at ~/.kde3/Autostart or something like that.
1) The toroot cheatcode still does not work for me.
If you have edited your linuxrc , Could you post your linuxrc in pastebin.com and post the link here, please
If you haven't edited it , check the md5sum of your linuxrc or download it again from the repo.
3) trying to build modules with right click, build module does build from folder contents.
Where's the issue ?

Regards,

Re: Porteus-v1_beta-i486 ready for testing

Posted: 07 May 2011, 23:16
by brokenman
Yes the kde/autostart folder no longer exists. With the upgrade to Trinity KDE came a folder with a new name (kde3). All previous paths that included ~/.kde should now be ~/.kde3. If the folder isn't there ust create it (Autostart). The next release will be tomorrow so perhaps you could wait for that.

The right click servicemenu for creating a module points to /opt/porteus-scripts/konqueror/create-module which is a script that uses 'dir2xzm'. The module creation may take some time but you will be notified when it has completed. (At least this is the way it is in the rc1 release coming tomorrow).