Porteus-v1.1rc2-i486 ready for testing

[brokenman]

If not let us know what we can do to help.

[francois]

Do you need some testing on MSI 340x laptop 32bit with two years of age with intel wifi and graphic cards and/or on hp pavilion 2713ca 64bit (bcm4328 wifi, nvidia 7150m graphic driver)? If it is not too late and if you are not in a hurry, this could be possible.

[Seq_Res]

@Ahau,

I did the experiment following your instructions. Now, V09 boots up V1.1 like a charm, just as it
had done on these public PCs. Thanks !
I always use 'always fresh'. since partitions were in FAT32. One minor thing is, every time command
"startx" have to be used to start X, and only "root" is acceptable to run it. I know the reason. Really a
minor thing it is. No any error happened when run applications.
Salute !

[brokenman]

Great news, and a testament to Ahau's experience.

After re-reading ... essentially you are just upgrading porteus without upgrading your bootloader. It could not fail. My doubts were unfounded.

[fanthom]

@Seq_Res

In my view, V09 is much better, since it booted all the public computers available for me.
I hope V1.0, V1.1 and 1.x to 2.x, 3x may keep its universality.

unfortunately not as syslinux-3.86 (can't remember exac version now used in v09) doesn't support ext4 which is currently a standard in the linux world (not to mention btrfs) . as far as i know you are the only one who reported syslinux troubles so we rather wont sacrifice ext4 for as little as one user. sorry about that.
glad that community figured out the workaround.

[Ahau]

I have also heard of other users who can't get syslinux v 4.04 to boot on HP computers -- since that is a known issue, hopefully future releases of syslinux tools will contain a fix.

[brokenman]

syslinux is moving forward
Stable release 4.05 / December 9, 2011; 6 days ago
Website http://syslinux.zytor.com

[ndiamond]

When a user boots with copy2ram, they probably want to remove their boot medium.

If their ISO file is on a USB drive and they booted with copy2ram and noauto, they still probably want to remove their boot medium.

If their ISO file is on a USB drive and they booted with copy2ram but not noauto, then they might be expecting their USB drive to be automounted, so I'm not sure what to do in that case.

To handle the combination of copy2ram and noauto, I suggest the following change in linuxrc:

Code: Select all

# finish
if param copy2ram; then
    [ "$EXTDEV" ] && umount /mnt/$EXTDEV 2>/dev/null && rmdir /mnt/$EXTDEV
    [ "$BOOTDEV" ] && { umount /mnt/$SGNDEV 2>/dev/null & rmdir /mnt/$SGNDEV; SGNDEV=$BOOTDEV; }
    umount /mnt/$SGNDEV 2>/dev/null && rmdir /mnt/$SGNDEV
    ........

--->

Code: Select all

# finish
if param copy2ram; then
    [ "$EXTDEV" ] && umount /mnt/$EXTDEV 2>/dev/null && rmdir /mnt/$EXTDEV
    [ "$BOOTDEV" ] && { umount /mnt/$SGNDEV 2>/dev/null & rmdir /mnt/$SGNDEV; SGNDEV=$BOOTDEV; }
    if [ "$ISO" != "" ]; then
        losetup -d /dev/loop0
        umount /mnt/$SGNDEV 2>/dev/null && rmdir /mnt/$SGNDEV
        if [ "$AUTO" = "noauto" ]; then
            echo $i"[1;36m""finished copying to RAM - booting media can be removed safely""[0m"
        fi
    else
        umount /mnt/$SGNDEV 2>/dev/null && rmdir /mnt/$SGNDEV
    fi
    ........

[fanthom]

welcome on board ndiamond,

i dont think that 'auto' or 'noauto' should matter in this case. i would agree that booting with 'from_iso=' + 'copy2ram' + removable media should unmount usb stick automatically.
'noauto' affects only Slackware part of booting process (rc.S script) and makes no difference for linuxrc.

i'll check this combination: 'from_iso=' + 'copy2ram' + removable media
and make sure that stick gets unmounted.

i hope i understood everything correctly, if not please correct me.

[brokenman]

Also keep in mind that a person using these cheats may NOT want their USB device to unmount as in the case that they have a portable OS and on the portable device they have a storage folder in which to keep stuff they download or transfer from the system.

[fanthom]

Also keep in mind that a person using these cheats may NOT want their USB device to unmount

'noeject' cheat prevents unmounting removable media when copy2ram is used.
no worries - pretty everything is covered

[francois]

On a hp pavilion 2713ca, everything works fine with rc2.

[Hamza]

You can share your configuration so we will know on which system Porteus is perfect

[francois]

In fact, I spoke too fast. Using my modules from porteus v1.0. Instead of activating them, porteus v 1.1 rc2 extracts them. What is going on here?

[Ahau]

francois, if I recall correctly, that was a known bug that should already have been dealt with -- I screwed up with the pcmanfm service menus, and instead of opening your module with 'activate', the double click defaults to my script to extract a module. I'll verify this is fixed in 1.1 final (due out tomorrow) -- just to make sure, was this in KDE or LXDE?