Wishlist for porteus 3.1

[tome]

"hmm... i can run multiple firefoxes here. what is the manger?"
Sure multiple? Another profile (bookmarks, history, settings) in two windows or the same?
Manager is Firefox Profile Manager.

[Bogomips]

@Rava
sse2 requirement is a break dealer. this is a list of unsupported processors:

Code: Select all

Pentium III  	NO
Celeron   < 1.7 GHz not likely, 
AMD Atlon XP/MP   NO
AMD Sempron   Socket 462: NO

Have Sempron, PaleMoon installer did not complain and installed. Thereafter could not open from menu bar, as caused PM abort. Then did manual install, could run YT videos but not open tabs or menu bar items without PM abort.

SeaMonkey is just about the only browser I can use on Porteus, does not have bloat of Firefox, and as well able to be kept under control. Also a mainstream browser, in that good add-on selection available. Tor browser doesn't present a problem, except at times, not being able to co-exist with SeaMonkey.

[Slaxmax]

Adding PaleMoon as slim, optimized Firefox variant (It's 100% Mozilla Firefox code, they just leave out all that only fed and bloat the fox...) that can run almost all FFx plugins...

Pale moon crashes here (kde4)
same error in palemoon forum
http://forum.palemoon.org/viewtopic.php?f=37&t=4956

@Bogomips

Try midori browser

[Bogomips]

Thanks Slaxmax. Elementary has Midori, and not too keen on it. However link proved useful, as have experienced exactly same symptoms and error messages.

now use 'kde42-oxygen', but any theme other than 'oxygen-gtk' should work

So when I've worked out how to change gtk2 theme to any theme other than 'oxygen-gtk' , will give PaleMoon another shot.

[Rava]

Thanks folks, I had no idea PaleMoon could be the source of so much issues since it works fine on my multi core more recent machines, and also on my one older mono core Samsung Q40 one...

...

Maybe I work on a pBuild script for creating the most recent PaleMoon / making it more easy creating it... but it seems I have to add some extra stuff since the PaleMoon tgz lacks some needed files...

Try midori browser

Nice browser per se... but when running XFCe at least it's requirements that have to be added are way larger than the browser module itself (and when I create such a test system, I try to always minimize the dependencies...)

[brokenman]

It looks like adding a virtual keyboard will also have to be retracted. Adding florence pulls in 5Mb of overhead and the lighter xvxkb segfaults (at least on 64bit). Perhaps a separate module bundle containing all dependencies can be made instead.

[Ed_P]

Another wish:

It would be nice if the extramod= cheatcode worked similar to the changes=EXIT: cheatcode in finding directories/folders.

With the changes=EXIT: cheatcode it isn't necessary to include the drive's path for it to find the file.

changes=EXIT:/porteus/changes/porteussave.dat works.

But extramod=/porteus/modules does not. It has to be specified as extramod=/mnt/sda5/porteus/modules.

[brokenman]

That is the intended functionality. I (for example) keep my extra modules on a separate partition. They are totally separate from the porteus partition.

[fanthom]

ok - will see if i'll be able to get 'extramod=' cheat to work without providing a full path.

thanks

[Rava]

Best would be:

extramod=/porteus/modules -> expands into "/mnt/BOOTDEVICE/porteus/modules" whereas BOOTDEVICE sure is the device Port booted from, while still having
extramod=/mnt/sda5/porteus/modules
working literally as it is.

[brokenman]

Perhaps partition by UUID would be suitable for portability where sda5 is /mnt/sda5 is converted to UUID. This way extramod can reside on removable media and it will always be found.

[Rava]

^
yes, UUID should be supported by all cheatcodes about a file or folder...
</Rava's 2 cents>

[Ed_P]

ok - will see if i'll be able to get 'extramod=' cheat to work without providing a full path.

Thanks fanthom.

Best would be:

extramod=/porteus/modules -> expands into "/mnt/BOOTDEVICE/porteus/modules" whereas BOOTDEVICE sure is the device Port booted from, while still having
extramod=/mnt/sda5/porteus/modules
working literally as it is.

Yup. It makes for Porteus on portable drives much easier to work with.

yes, UUID should be supported by all cheatcodes about a file or folder...

Supported, yes. Required, no.

[tome]

Code: Select all

# Get booting device and link to it
bdev=`grep -A1 "Booting" /var/log/porteus-livedbg|tail -n1|sed 's^//^/^g'`
pdat=${bdev}
ln -sf $pdat /mnt/bootdevice

it would be better than uuid because it is the same for all devices (uuids are different), I miss it (or similar) in Porteus

[Rava]

Yup. It makes for Porteus on portable drives much easier to work with.

IKR!

Supported, yes. Required, no.

That's what I meant.
___________________________________

Off Topic... (kinda)

Code: Select all

# Get booting device and link to it
bdev=`grep -A1 "Booting" /var/log/porteus-livedbg|tail -n1|sed 's^//^/^g'`
pdat=${bdev}
ln -sf $pdat /mnt/bootdevice

it would be better than uuid because it is the same for all devices (uuids are different), I miss it (or similar) in Porteus

I wonder, which code is more streamlined, tome's above or mine:

Code: Select all

awk 'c-->0;/Booting device:/{c=1}' /var/log/porteus-livedbg

And being the lazy virtual console user that I am, I create the symlink "/x" that links to the current boot device. Why /x one might ask? For one, cause there is no folder with "x" in the root directory of any Linux I know... and it's just one character to type, therefore typing e.g. "/x/p[tab]b[tab]" will always give me /x/porteus/base aka the base folder of the current booted Porteus... </lazy>