late reply is late, but busy Rava was busy...
fanthom wrote:@Rava
"Do we already have a thread for collecting the software and chatting about which one to use?"
will create one soon
[..]
"And fanthom, you should make some rules about creating GPU driver modules, like "include all necessary stuff in the module" like the rc.deactivate.nouveau or such..."
ok will try to gather all necessary info in one place (need to find some time first)
I could create a forum thread in "General / development" and put in my thoughts / rules about NVidia at least in there if that's okay with everyone.
I cannot give any ideas about ATI since I don't own a single PC with such a GPU.
fanthom wrote:
"How do we want to handle issues like with truecrypt in the future.
It only works when run by root."
module creators can use a script in /usr/local/bin which uses "switch to root function"
will add it to the module creation rules
I suggest we also create a thread in "General / development" for that for discussing such matters and for the best ways to solve them, since for every program we port to Porteus the one creating the module not needs to re-invent the wheel over and over again...
Again, i could create such thread initial post if that's okay with all of you.
Does the "switch to root function" script already exists?
___________________________________________________
from
boot/docs/bloaders.txt
df -T /dev/xxx (where xxx is your partition - sda/sdb)
With the rare occation of some weird USB pendrives, that won't work like the above.
In my case:
Code: Select all
root@porteus:/mnt/live/memory/images# df -Tm /dev/sda
Filesystem Type 1M-blocks Used Available Use% Mounted on
- - 1511 1 1511 1% /dev
Since the device is *not* sda but sda1. It works for fdisk like above, but not for df.
Well, with the exception of the rare USB pendrives when the mounted device really is named /dev/sdc and not sdc1... but all I know is that they brake some fvat rules by doing so, to get some few more kB on the stick, as it seems...
So I suggest this:
df -T /dev/xxxn (where xxx is your partition - sda/sdb and n is the partition number. If you are unsure about the partition number, cd into a directory of you know that is on that partition, like the boot/ folder on your hard drive or USB pendrive, and then run a "df -T . df then tells you the exact device name and mount point.")
___________________________________________________
fanthom wrote:you must have kxkbrc file for each user in the system. config files are not shared between users - it would make no sense (one prefer ice creams, second lemonade)
Ahhh good to know, what is the syntax of that file? man kxkbrc not exists...
I tried editing /home/guest/.config/autostart/xkb.desktop
Code: Select all
Exec=setxkbmap -layout de,uk -option "grp:alt_shift_toggle"
but that ended weird. Every time I switched the language to "German" and started a new program, the keyboard was set back to "UK" again...
___________________________________________________
Speaking of man files...
When starting "man" with an existing man page, like "man bash" and I exit "man", nonetheless links is started doing an online search for the very same manfile.
How could that be undone? Usually I am quite content with the "on-board" man-files and don't need any additional ones that needed to be loaded each time...
___________________________________________________
And about activate and LXDe menu entry...
I tried that with my opera 64 bit module, first copied the xzm to /tmp to have a "copytoram" effect, then I run "activate" as root on that module.
I got the on-screen windows telling me the module was loaded successfully, but there still is
no entry of Opera in [menu]/Internet...
Opera was put there when I put the module in my rc1 posteus/base folder, but it should work with later started modules as well...
Since "activate" still not uses a version number, all I can give you is its md5sum:
Code: Select all
f56d4d90b718b804db5783a9785af70b /usr/bin/activate