Porteus

Hi fullmoonremix and brokenman

Thank you for responding and helping.

I'm going to use brokenman's idea of permissions on the rc.FireWall file as it's the easiest
but it's nice to know there are options.

Dave

Hi all

Any one know how to permanently set firewall to off?

Using a Porteus box for quick http tests on an intranet and it's a pain to every time go into System Tools --> Porteus Setting Centre --> ......

Running Desktop Edition v3.0 (kernel 3.13.6) LXDE

T.I.A.

Dave

@Rava I'm not saying that you are making it up or that the BIOS manufacturer is trying to hide something. I'm only saying that between the way your (any) BIOS handles RAM, possible video RAM sharing, kernel reserved memory, memory used by some drivers, shadowing of the BIOS and so on most if not all...

Rava wrote: You are right with the BIOS shadowing itseld into RAM, but that's a very smaller amount of Memory, not 512 MB of it for shadowing the BIOS! I agree that BIOS by itself is not going to take up 512MB, but it will be quite large as much of the BIOS contents are compressed and then expanded ...

Ed_P is correct, many video cards "borrow" main system memory plus of course the BIOS also uses some.
Most motherboards "shadow" the BIOS, meaning that the BIOS contents are first loaded into RAM then run from there
as RAM is much faster than flash rom.

@Rava So, in short, nope, ":" is not a comment! Correct and the easy way to test it as follows: This works as there is a command in the function even though it does nothing: DoNothing() { : } While this will not work as there is only a comment: DoNothing() { # let's do nothing }

Hi Rava

Interesting point about : and #

Have a look here:

http://stackoverflow.com/questions/1240 ... op-in-bash

@Bogomips Rather like your goto in Bash, reminds me of the old Basic days. Actually your post got me thinking, how much could one replicate the Basic language in Bash. Bash has no means of creating macros like in MASM or NASM but it does have the "source" command and when used with functions, we cou...

Hi ncmprhnsbl

Fantastic, exactly what I was looking for, a simple solution without the need to download anything else
as feh is not shipped with desktop version by default.

pcmanfm --set-wallpaper /to/your/wallpaper.svg

Many thanks, works a treat.
Dave

Hi ncmprhnsbl

Yes I can set a svg using the rightclick--> desktop settings.

The svg's are being generated by a Bash script and I can set them to be put anywhere.

Will look into feh, thank you.

Dave

Hi all

Been pulling my hair out trying to change the wallpaper programmatically.
Using desktop V3.0 (kernel 3.13.6-porteus) and using lxde.

I need to change wallpaper with different SVG images which are dynamically generated.

Any assistance in this regard would be greatly appreciated.
T.I.A.
Dave.

Thanks fanthom.

I'm actually very glad I made a mistake with the two versions of vmlinuz as it forced me to investigate further
and in doing so taught me a lot about the "nitty-gritty" of Porteus which I otherwise would have just glanced over.

Dave.

Another method to check for which vmlinuz is which (for those that also change them around) is: strings /path/to/vmlinuz | grep porteus It will return either 3.13.6-porteus (plus some other info) or 3.13.6-porteus-kiosk. The 3.13.6 version number will change according to the one that is being used.

Right solved, my silly mistake. Got confused between the vmlinuz from desktop and kiosk and was still using the one from kiosk. The way I found it was looking at the contents of both vmlinuz files. The one from kiosk points to 3.13.6-porteus-kiosk at offset 0x03150, whilst the one from desktop point...

OK another update. Found that the second "kernel" i.e. 3.13.6-porteus-kiosk is being created from 001-core.xzm Should I rather take it out (the directory that is) and thus only have one "kernel" i.e. the one from 000-kernel.xzm (from the desktop edition)? If so, will it not have other repercussions ...