Page 1 of 8

Porteus-v1_beta-i486 ready for testing

Posted: 19 Mar 2011, 11:07
by brokenman
Porteus v1 Beta 32bit is released.

- kernel 2.6.38
- latest LXDE from git (1st of March by Ponce!)
- New lxde iconset Humanity
- Userland bumped to slack-current
- Prompt during boot to change default password (from 64bit)
- modesetting dumped and back to noveau

/boot
- linuxrc now fully support 'lazy' devices (slow usb/cdrom which needs extra time for initialization). Still: 'delay=' cheatcode is required to discover lazy device when you are not using it directly for booting.
- added 'fumount' function to cleanup script. if umount point is 'busy' during umount procedure then is remounted 'ro'.
- added 'nomagic' cheatcode. updated /boot/porteus.cfg 'Always Fresh' mode and /porteus/cheatcodes.txt
- added extlinux for booting from ext2/3 partitions with syslinux menu
- added /doc folder for documentation (Ahau)
- added scripts folder for boot scripts
- added win_start_here.hta and lin_start_here.sh for start scripts. These are the files that should be run when installing Porteus.
lin_start_here.sh is a console script, win_start_here.hta is a windows Hypertext Application using the splash screen as menu.

/porteus
- rc.M is now creating an xzm module if default passwords are updated. Move it to /porteus/modules and you wont be prompted for changing passwords anymore.
- kactivate/kdeactivate are replaced by xactivate/xdeactivate
- lzm modules are automatically converted to xzm during activation
- porteusmodman is rewritten on xdialog
- modtools written for xdialog
- added ndiswrapper
- squashfs-tools bumped to 4.2
- added 'Default login' info to kdm/lxdm wallpapers
- Added to 001/usr/bin/changes-time script
- added xpns-tool: a xdialog version of pns-tool.

Interesting new packages
librsvg
xdialog
python-2.6.4
wicd

CLI
pns-tool (text version of xpns-tool)
changes-time.sh (saves system changes made in a given time)
save-changes (saves /mnt/live.memory/changes to a module)
extpkg (extract a package from base module or running Porteus)
rempkg (remove a package from base module or running Porteus)
ctrl + c/v to copy & paste from konsole

Important points:
I have experienced freezes after using installpkg or ac/deactivating certain modules. Please report if you experience this so we can gauge how widespread the problem is.

Some dual graphics systems with graphic switching function will experience kernel oops if no ATI driver is present.

High power usage on graphics switching systems (switcheroo) as high power. There is a kernel module available that allows acpi calls: https://github.com/mkottman

To remove the startup pause at default password check ... just enter your new passwords and continue to GUI. Copy the module /home/Desktop/psswd.xzm into your Porteus/modules folder and Porteus will pick it up and bypass the startup pause. This is a much needed security feature.

Enjoy and please post issues here: :beer:
Brokenman

Posted after 3 hours 42 minutes 43 seconds:
Hold off downloading, will just fix a theme related problem and post when it is ready.

Posted after 1 hour 30 minutes 10 seconds:
I've made a quick to the xmodtools file. Instead of rebuilding the module on the server i decided to just it in rootcopy for now. Please let me know if you get a blank box when opening the xmodtools help page.

Re: Porteus-v1_beta-i486 ready for testing

Posted: 19 Mar 2011, 15:24
by Blaze
About bugs of Porteus-v1_beta-i486

1. Need to replace orange/red color http://img836.imageshack.us/img836/1657/1sss.jpg

2. When i boot up Porteus-v1_beta-i486 i observe this error:

Code: Select all

ERROR: Module psmouse does not exist in /proc/modules
3. When LXDE is started i see it http://img838.imageshack.us/img838/849/1234ot.png

4. Image

5. Where is a gtk theme?
Link: http://www.motolink.ucoz.ru/water_vapor.sq4.lzm

About Porteus-v1_beta-i486 or IMHO
a) When i boot up Porteus-v1_beta-i486 - I don't like helps on English language about save.dat (unfortunately many of users do not know English language)
and tweak porteus.cfg with add cheatcode for save.dat (unfortunately it's hard for many newbies)

Suggestion:
b) It is necessary to make a Porteus easier for newbies (noobs) if it's possible (about save.dat)
c) What do you think about these KDE startup sounds?
Link: http://www.motolink.ucoz.ru/sounds.rar (9 choice sounds)

Re: Porteus-v1_beta-i486 ready for testing

Posted: 19 Mar 2011, 15:34
by Hamza
Why , we don't translate the initrd in some language , for the users who do not speak english.

I can translate the initrd in French.

Regards

Re: Porteus-v1_beta-i486 ready for testing

Posted: 19 Mar 2011, 15:43
by Blaze
Hamza, this is good idea!

For language definitions need to use cheatcode

Code: Select all

lang=your_language
and initrd select your language for it when users boot up Porteus.

I can localization on Russian too, but i need how to about tweak initrd.

Thanks.

Re: Porteus-v1_beta-i486 ready for testing

Posted: 19 Mar 2011, 20:18
by brokenman
1. Need to replace orange/red color http://img836.imageshack.us/img836/1657/1sss.jpg
I like the red, as imprtant info stands out. What color do you suggest?
2. When i boot up Porteus-v1_beta-i486 i observe this error:
ERROR: Module psmouse does not exist in /proc/modules
Damn, i fixed this already and had to restore 002-xorg and forgot to do again.
Please remove psmouse lines from /etc/rc.d/rc.local
3. When LXDE is started i see it http://img838.imageshack.us/img838/849/1234ot.png
chmod 4755 /usr/libexec/dbus-daemon-launch-helper
(unpack 002, and chmod there then repack)
last minute problems with existing theme, will apply this theme now (water vapour)
About Porteus-v1_beta-i486 or IMHO
a) When i boot up Porteus-v1_beta-i486 - I don't like helps on English language about save.dat (unfortunately many of users do not know English language)
and tweak porteus.cfg with add cheatcode for save.dat (unfortunately it's hard for many newbies)
Not much we can do about that. It would be nice to have every language but lots of work and more space. Perhaps (as mentioned below) initrd can be translated.
Suggestion:
b) It is necessary to make a Porteus easier for newbies (noobs) if it's possible (about save.dat)
I agree. Any ideas?
c) What do you think about these KDE startup sounds?
Link: http://www.motolink.ucoz.ru/sounds.rar (9 choice sounds)
Will check these out.

Once again, thanks for being right on top of this and testing immediately with a thorough description of problems.
PS: your module icon is way cool!

Re: Porteus-v1_beta-i486 ready for testing

Posted: 19 Mar 2011, 21:19
by Blaze
What color do you suggest?
for example:

Code: Select all

LemonChiffon1 #FFFACD
Cornsilk1 #FFF8DC
Honeydew1 #F0FFF0
LavenderBlush1 #FFF0F5
Look at these styles color-html
Perhaps (as mentioned below) initrd can be translated.
for initrd.lz

Code: Select all

mv initrd.lz initrd.lzma
lzma -d initrd.lzma
mkdir /mnt/initrd
mount -o loop initrd /mnt/initrd
lzma -z initrd
mv initrd.lzma initrd.lz
How to make this for initrd.xz ?

Re: Porteus-v1_beta-i486 ready for testing

Posted: 19 Mar 2011, 21:55
by brokenman
xz -d initrd.xz #unpack
mkdir /mnt/initrd
mount -o loop initrd /mnt/initrd #loop mount
xz --check=crc32 --x86 --lzma2 initrd # repack as .xz

EDIT:
I've just patched the iso on the server:
fixed lxde boot error
added water_vapor gtk theme
removed rc.local psmouse reference

Re: Porteus-v1_beta-i486 ready for testing

Posted: 20 Mar 2011, 00:37
by wread
In boot/porteus.cfg MENU WIDTH should be =32 instead of =30, so the title line displays at end "32 bits" instead of "32 bi".

That is an easy one to correct! :)

Cheers!

EDIT: Now I have all necessary modules for HP-Printing converted. BTW, python 2.6.4 is not enough for hplip. I had to use a python-2.6.6 to get it working, so hp-check says again no errors or warnings. In V09 I had added python-2.6.6 to the 007-devel.lzm modul and renamed it to 007-develp.lzm; the p at the end to remember that python was now included. I think you did something similar, but with python-2.6.4 and no "p" added at the end. For the hp-printing new modules, I will make a tar ball and put it in a repo.

All in all, Fine Business, Brokenman, Congratulations again!

Of course, we will have to add a Settings>>Printer (a KDE Control, CUPS-based,I think, as per V09) to the main menu....

Good night!

Re: Porteus-v1_beta-i486 ready for testing

Posted: 20 Mar 2011, 07:40
by Blaze
Blaze wrote:Suggestion:
b) It is necessary to make a Porteus easier for newbies (noobs) if it's possible (about save.dat)
brokenman wrote:I agree. Any ideas?
My a new suggestion for it.

Need to copy save.dat to rootcopy of ISO Porteus and will to realise this:

Image
Note. To use two cheatcodes

Code: Select all

changes=save.dat
for Windows filesystem

Code: Select all

linuxfs=/porteus/
for Unix filesystem
This cheatcode will need to make

Re: Porteus-v1_beta-i486 ready for testing

Posted: 20 Mar 2011, 15:31
by fanthom
@Blaze
"Need to copy save.dat to rootcopy of ISO Porteus"
this is not very flexible solution as save.dat containers will have only certain sizes (512MB, 1024MB, 2GB, etc...). I would like to give the users freedom of choice: if user wants 10GB save.dat (or for example 300MB) then he can create it with existing linuxrc solution.
i would prefer Hamza's suggestion with translated initrd messages. but this can cause other problems:
- who will be doing translations and for which languages?
- how to verify if translation was done correctly (no misleading informations)?
- what to translate (whole linuxrc or just 'save.dat creation' part)?
- what about other scripts? rc.S, rc.M, scripts like pns-tool, LST, porteus_encrypter, etc....
- what about all documents in /boot/docs?
- should we translate also /boot/porteus.cfg?

i think it might be to much troubles for our small community :(

@all
my proposition for now:
1) go with save.dat in /porteus folder like in slax. (requires rewriting of installation dosc + installation scripts - user must know that this file is there and it must be used together with FAT/NTFS). disadvantage: save.dat has limited choice of sizes.
2) translate just 'save.dat' creation part of linuxrc. i can export this function to a separate file like 'fatal' is now. so we would have for example /initrd/lang/save.en (default); /initrd/lang/save.fr; /initrd/lang/save.ru; /initrd/lang/save.de. etc...
i could call this function from linuxrc when necessary with proper language choice.

What do you think?

Re: Porteus-v1_beta-i486 ready for testing

Posted: 20 Mar 2011, 15:39
by Hamza
I can translate all rc scripts , i have done that with Adrio.

I can translate Initrd in French.

Regards

Re: Porteus-v1_beta-i486 ready for testing

Posted: 20 Mar 2011, 18:45
by Blaze
fanthom, probably you are right, but I think easier to go my way with two cheatcodes plus your suggestion.

If other users wants freedom of choice, they can to make a save.dat with script (additional tool in menu of kde).

Code: Select all

Description: This script will automatically to create and copy a save.dat with the chosen size to ISO of Porteus.
By default for ms partition (win filesystem) will be created save.dat with size 1024MB.

Re: Porteus-v1_beta-i486 ready for testing

Posted: 20 Mar 2011, 20:39
by crashman
1 - Create Module in rightclick menu bad work if it create bigger module then .xzm module is empty but if use convert option then module is good. Tested in mesa-7.8.1-i486-1.txz.

2 - why in after converted option module is automatic activated ? this is not good option if double click work fine.

3 - Wicd doesn't connect to network always show 'bad password' but if connect via console network work fine. I use on wep hex encryption.

4 - xorg work better than porteus alpha but in 3d xserver crashes in my ati xpress200m graphics card

Re: Porteus-v1_beta-i486 ready for testing

Posted: 20 Mar 2011, 20:48
by Hamza
For password , you need install the libs of encryption.

Regards

Re: Porteus-v1_beta-i486 ready for testing

Posted: 21 Mar 2011, 06:43
by brokenman
I think a mixture between blaze and fanthoms ideas would be good. A save.dat is created during boot (maybe in chosen language) and then a GUI tool could be made so user can create their own save.dat.
Create Module in rightclick menu bad work if it create bigger module then .xzm module is empty but if use convert option then module is good. Tested in mesa-7.8.1-i486-1.txz.
Sorry i don't understand
why in after converted option module is automatic activated ? this is not good option if double click work fine.
The right click converts only sq3 module. It doesn't activate after converting (at least not for me). sq3 modules will be converted and activated by double click. It means users don't need to convert first ... just double click.
Wicd doesn't connect to network always show 'bad password' but if connect via console network work fine. I use on wep hex encryption.
I will have to look at this. I don't have access to WEP so couldn't test ... if you get it working with extra libs let me know and i will add them.
In boot/porteus.cfg MENU WIDTH should be =32 instead of =30
Thanks. Will add extra 2 bits.