Porteus

@Falcony
brokenman like it so it's decided: we are switching to 'xzm'. lzm wont work with 1.0 in any way. I have converted all scripts for 64bits already

I could also add in auto conversion if user tries to activate .lzm module after asking user.

@brokenman
good idea - activate script could check if module ends on '.lzm' and then suggest conversion
(i hope we will be able to catch up all the changes made by both of us in all scripts and port them to 32/64 bits respectively.)

i have finally found how to pack initrd with xz compression to be recognized by the kernel
syntax is quite tricky: now vmlinuz+initrd.xz gets only 0.7 sec in Vbox to start linuxrc

I wrote script which download automatically all *.lzm modules
from
http://code.google.com/p/fidoslax repository

convert it witn new compressions *.xzm and upload
to new repo

http://code.google.com/p/fidoslax-32

Now new repo contain more then 800 *.xzm modules

@fantom, brokenman - so 32-bit betas to test - whould be nice to have L)

@Falcony
well done with .xzm repo

i know that many people would love to try first BETA. We have resources:
- LXDE is ready: need to track just one bug
- KDE-4.6.0 should be done next week
- Trinity (alpha) should be ready next week as well

The plan was to release first BETA when kernel 2.6.38 is out. This should be done in 4-6 weeks.
I could release early ALPHA (and brokenman probably as well) next week but there are 2 things which are stopping me:
- grub4dos installer for Windows
- package manager for Porteus

Here is the deal:
You will give me two things mentioned above - i will give you first alpha straight away.

Cheers

@fanthom,

to late to deal, brokenman already release alpha 32-bit version L)

But anyway please see http://forum.porteus.org/viewtopic.php? ... 1227#p1227

and try http://falcony.googlecode.com/files/gru ... .2.tar.bz2

This tarboll contain installation batch script grub2usb.bat for Windows - to install Porteus/FIDOSlax from Windows to USB

HDD installation program quite messy as Windows 7/Vista but when I have time - I would manage it also

"to late to deal, brokenman already release alpha 32-bit version L)"

This is only an alpha release to road test Trinity. Alot of the Porteus functionality has not yet been added. I think a package manager is most important. I'd like to write one unique to Porteus but not enough time.

Will we be using this installer to replace existing syslinux/extlinux? I've tested the new extlinux on FAT32/ext2/3 and works good. Havn't yet tested your installer Falcony but will do so.

packager manager - is qute mess thing to do Д)

Regarding syslinux/extlinux - I will keep it together as grub4dos

For ex. extlinux allow to boot from hd0,0 with ext4 file system
grub4dos - no