Porteus tips and tricks

[francois]

One more clarification though, if I may. Does that mean that kernel headers and kernel sources from other distributions are any different from what we call the crippled sources?

Regards.

[fanthom]

"Does that mean that kernel headers and kernel sources from other distributions are any different from what we call the crippled sources?"
yes - porteus crippled sources are just stripped version of full kernel sources. after compilation, full sources takes around 900MB while crippled just 38MB.
crippled sources contains kernel headers + aufs files + kernel config and are specific to porteus version (you cant use crippled sources from porteus v09 in v1.0)

Cheers

[francois]

Hi all,

...
Hi Ahau, could you reedit you first post to mention the copy2ram cheatcode in some way, as we have it. It could be useful for dissemination of porteus on the net:
http://forum.porteus.org/viewtopic.php? ... 3036#p3036

I am looking for a reference to mention that we have this feature in porteus as well. I would use this post as a citation so that we appear in Wikipedia's List of Linux distributions that run from RAM:
Lightweight Linux distribution: Distributions described as lightweight

In addition, in the recent CD's the cheatcodes.txt appear now in /boot/docs, is it possible to take into account of this modification in the first post of this thread.

Naturally, these are only suggestions.

Finally, less necessary as I made a post to clarify the issue of the copy2ram cheatcode:
http://forum.porteus.org/viewtopic.php?f=39&t=444

[Ahau]

Edited original post to include suggestions, thanks everyone!

Please review and provide feedback or suggestions for other tips and tricks. If no further edits are needed, I'll publish this on the website on Monday.

I need to know the key combination for item 13 (opening dmenu in LXDE) -- if no one knows it, I'll delete that item from the list.

Thanks, all!

[82issa]

Alright bud I believe I found the info on the dmenu thing.
Where it was hiding
~/.config/openbox/lxde-rc.xml

Code: Select all

<!-- Keybind for dmenu -->
    <keybind key="A-F3">
      <action name="Execute">
        <command>/usr/bin/dmenu-bind.sh</command>
      </action>
    </keybind>

keybind key="A-f3" I am translating to alt+f3

I tried out on my 64bit rc2. I am not familiar with this but.
I think this is what we are looking for here.

Posted after 30 minutes:
Oh another thing. These tips and tricks. Would make some great slides for an Installer. You know how most installers have those kinda lame slide shows towting there features while there progress bar pretends to be doing something important.

[Ahau]

Thanks. 82issa!

Not a bad idea RE: the slides during install, except...our install takes about 1 second (just long enough to write 512 bytes).

Actually, sometime I'd like to make an install video, and see how short I can make it.

Posted after 2 days 23 hours 55 minutes 3 seconds:
Update -- I added a tip for using magic folders. I also created titles for each tip, so that I can link them from a table of contents once I have this on the main site. I've reordered them a little bit as well.

Posted after 5 days 22 hours 13 minutes 16 seconds:
A big thanks to Hamza for his unseen efforts to save my ass on this one!

Also, the document has been published to the main site, and removed from the first post in this thread, replaced with a link. I'll be doing this with more of our documents, to help reduce multiple versions of the same docs to keep updated. The threads will stay active for folks to continue discussing and asking questions.

Thanks, all!

[Allias]

This document has been moved to the main site, please read it here:

http://porteus.org/info/docs/45-other/1 ... ricks.html

Feel free to continue discussing this document, ask questions, or suggest changes in this thread.

Thanks!

Great job, your HOW-TO s are very good for beginners like my self keep up the good work!

[francois]

Ahau is for sure the king, if not the emperor of the documentation.

[don570]

On a non-windows machine the time is set wrong.

If you notice this then here are the instructions
as root user or super user --->

The time needs to be 'gmt' rather than 'localtime'.

The way I did this-->

1) Boot Porteus from CD ( or a hard drive partition)

2) At the terminal type
mkdir -p /var/log/setup/tmp

3) Then type
touch /var/log/setup/tmp/utc

4) Launch from terminal the app 'timeconfig'
and set correct timezone

5) logout and log back in
Your time should be correct now.

__________________________________

[bigbass]

have the Porteus version and the time display in the title bar of your terminal

edit
/root/.bashrc

and add this to the end

Code: Select all

function xtitle()      # Adds some text in the terminal frame.
{
    case "$TERM" in
        *term | rxvt)
            echo -n -e "\033]0;$*\007" ;;
        *) 
            ;;
    esac
}
xtitle= xtitle `cat /etc/porteus-version` `date`

[kevjonesin]

The link at the top of this thread ...

This document has been moved to the main site, please read it here:

http://porteus.org/info/docs/45-other/1 ... ricks.html

... is dead/broken. Leads to ...

"500, View not found [name, type, prefix]: phocadocumentation, html, phocadocumentationView"

[fanthom]

thnaks - will go through the whole porteus website during next two weeks as it got outdated a bit.
wont be able to track all forum links i'm afraid...

[long123]

The cheatcodes.txt file just isnt very clear on how it works and which changes= to use. What I want is to set up the changes.dat file the first time I boot up and then never have to change it or load it again. Being a windows user I find the idea of having to type all this stuff out EVERY time I load the OS to be down right redundant and time wasting

[donald]

From cheatcodes.txt:

cheatcodes can be added to the APPEND line of your
/boot/syslinux/porteus.cfg entries...to apply them automatically on every boot.

There is no need to "type all this stuff out EVERY time"

[Ed_P]

The cheatcodes.txt file just isnt very clear on how it works and which changes= to use.

Ok.

What I want is to set up the changes.dat file the first time I boot up and then never have to change it or load it again.

Ok. That's the idea how it works and how it is done. You boot Porteus, you use the Porteus Setting app to create the porteussave.dat file, and then you have to manually change the porteus.cfg file to point to the porteussave.dat file you just created. And yes it would be nice if the app did that for you.

Being a windows user I find the idea of having to type all this stuff out EVERY time I load the OS to be down right redundant and time wasting

I think you'll find Linux and Android users feel the same way.

My cheatcode looks like so:

Code: Select all

changes=EXIT:/porteus3.0/changes/porteussave.dat

This option allows my changes to be saved to the .dat file when I shutdown Porteus rather than continueously.

So, after you create the save.dat file and change the porteus.cfg file, reboot. No more typing "all the stuff out EVERY time".