Porteus-v1.0-rc2-x86_64 "We are there" (almost)

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#31 by cttan » 12 May 2011, 09:45

Hi fanthom,

I have loaded the sendmail.xzm slackware 13.37 package downloaded from http://pkgs.org/slackware-13.37/slackwa ... 1.txz.html
After that, my root user is gone. When I lock the session, I'm not able to login back using my root password.
Any idea? Thanks in advance.

Another peculiar thing about this few releases is that, I can use my script to activate the packages without any problem. If I use double clicking on the package name to activate a package, the system would hanged/crashed and I would not be able to do anything other than hard reset using power button.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4547
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#32 by fanthom » 12 May 2011, 13:27

@Rava
"Do we already have a thread for collecting the software and chatting about which one to use?"
will create one soon

"What is the easiest way to edit the ISO to change the boot menu to my defaults, and to add some stuff like NVidia drivers?"
made your changes to /boot and /porteus then use /porteus/make_iso.sh script to create new iso (Ahau - please add this to the FAQ)

"And is there a cheat code that *disables* the loading of a certain module for this very boot?"
read /boot/docs/cheatcodes.txt

"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)

"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 "swith to root function"
will add it to the module creation rules

@cttan
"I have loaded the sendmail.xzm slackware 13.37 package..."
this is very rare example of a slackware package which deals with 'installpkg -root" incorrectly (txz2xzm uses this feature to create xzm module).
Please do a simple test for me:
"mkdir /tmp/new
installpkg -root /tmp/new sendmail-8.14.4-x86_64-1.txz"
now you can check that /tmp/new/etc/passwd has only one entry.
That's because doinst.sh script has a function which adds "smmsp" user to /etc/passwd and /etc/group:

Code: Select all

if ! grep -q "^smmsp:" etc/passwd ; then
  echo "smmsp:x:25:25:smmsp:/var/spool/clientmqueue:" >> etc/passwd
fi
if ! grep -q "^smmsp:" etc/group ; then
  echo "smmsp::25:smmsp" >> etc/group
fi
this function doesn't work properly with "installpkg -root" and should be rewritten as follows:
if ! grep -q "^smmsp:" /etc/passwd ; then
cp /etc/passwd etc/
echo "smmsp:x:25:25:smmsp:/var/spool/clientmqueue:" >> etc/passwd
fi
if ! grep -q "^smmsp:" /etc/group ; then
cp /etc/group etc/
echo "smmsp::25:smmsp" >> etc/group
fi
it's easier to create xzm module and remaster it before using:
"unsquashfs sendmail-8.14.4-x86_64-1.xzm
rm squashfs-root/etc/{group,passwd}
cp /etc/{group,passwd} squashfs-root/etc
echo "smmsp::25:smmsp" >> squashfs-root/etc/group
echo "smmsp:x:25:25:smmsp:/var/spool/clientmqueue:" >> squashfs-root/etc/passwd
dir2xzm squashfs-root sendmail-8.14.4-x86_64-2.xzm"
should work now :)

2) "Another peculiar thing about this few releases is that, I can use my script to activate the packages without any problem. If I use double clicking on the package name to activate a package, the system would hanged/crashed and I would not be able to do anything other than hard reset using power button."

please provide your script and example of a module which crashes porteus after double click. do you use your script in text mode or GUI?

Cheers
Please add [Solved] to your thread title if the solution was found.

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#33 by Ahau » 12 May 2011, 14:58

Add the following to FAQ on website:

How can I customize the Porteus ISO?
Make all of your desired changes to the /boot and /porteus folders to make them look exactly how they should appear on your custom ISO. Then run the script /boot/make_iso.sh. This script will create a new ISO with a name and location you provide.

Example:

Code: Select all

cd /mnt/sdXN/boot/
./make_iso.sh 
where sdXN is the location of your /boot and /porteus folders.


Let me know if I should change anything.
Please take a look at our online documentation, here. Suggestions are welcome!

cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#34 by cttan » 13 May 2011, 03:44

The sendmail is working perfectly now!!! :Yahoo!:
Thanks!

What I mean is after activated all my modules using the scripts the system is running without error. Is just when I want to activate another module(it could be any module) by double clicking it then the problem appears. The activation box would stayed on the screen and system hanged.

I know I can put all my modules in the modules folder in Porteus folder of my USB disk. I just want the system to boot up faster thats why I choose to start a script after system finished loading.

My Porteus script as below:-

Code: Select all

#!/bin/bash
echo 6 > /sys/class/backlight/acpi_video0/brightness
amixer -c 0 cset iface=MIXER,name='Master Playback Volume' 50%
amixer -c 0 cset iface=MIXER,name='PCM Playback Volume' 80%
if(lsusb | grep 13fe:1f00 > /dev/null) then
	if(mount | grep /dev/sdb1 > /dev/null) then
		umount /dev/sdb1
	fi
mount /dev/sdb1 -o ro
fi
if(mount | grep /dev/sda6 > /dev/null) then
	sleep 1
else	mount /dev/sda6
fi
if(mount | grep /dev/sda7 > /dev/null) then
	sleep 1
else	mount /dev/sda7
fi
swapon /mnt/sda7/swap
activate /mnt/sdb1/useful_mods_xzm/sbopkg-0.34.1-noarch-1ponce.xzm
activate /mnt/sdb1/useful_mods_xzm/git-1.7.3.5-x86_64-2.xzm
activate /mnt/sdb1/useful_mods_xzm/jre-6u24-x86_64-1.xzm
activate /mnt/sdb1/useful_mods_xzm/compat32.xzm
activate /mnt/sdb1/useful_mods_xzm/multilib-v09-B2.xzm
activate /mnt/sdb1/useful_mods_xzm/usb-modeswitch_1.1.7-1_amd64.xzm
activate /mnt/sdb1/useful_mods_xzm/usb-modeswitch-data_20110227-2_all.xzm
activate /mnt/sdb1/useful_mods_xzm/wvdial-1.61-x86_64-1ponce.xzm
activate /mnt/sdb1/useful_mods_xzm/wvstreams-4.6-x86_64-1ponce.xzm
activate /mnt/sdb1/useful_mods_xzm/minicom_2.4-1_amd64.xzm
activate /mnt/sdb1/useful_mods_xzm/lrzsz_0.12.21-4.1_amd64.xzm
activate /mnt/sdb1/useful_mods_xzm/nano-2.2.4-x86_64-1.xzm
activate /mnt/sdb1/useful_mods_xzm/putty-0.60.xzm
activate /mnt/sdb1/useful_mods_xzm/libglib1.2ldbl_1.2.10-19_i386.xzm
activate /mnt/sdb1/useful_mods_xzm/libgtk1.2_1.2.10-18.1_i386.xzm
activate /mnt/sdb1/useful_mods_xzm/gnutls-2.10.1-x86_64-1.xzm
activate /mnt/sdb1/useful_mods_xzm/opera-11.00-1156-x86_64.xzm
activate /mnt/sda6/linux/useful_mods_xzm/libreoffice-3.3.0-x86_64-1alien.xzm
activate /mnt/sdb1/useful_mods_xzm/samba-3.5.6-clientonly-x86_64-b03stripByZork.xzm
activate /mnt/sdb1/useful_mods_xzm/google-talkplugin_current_amd64.xzm
cp -a /mnt/sdb1/minirc.dfl /etc/minicom/
cp -a /mnt/sdb1/.dialdir /root/
cp -a /mnt/sdb1/wvdial.conf* /etc
cp -a /mnt/sdb1/resolv.conf /etc/resolv.conf
cp -a /mnt/sdb1/wireless-settings.conf /etc/wicd/
/etc/rc.d/rc.wicd restart
mkdir /root/.opera
cp -a /mnt/sdb1/bookmarks.adr /root/.opera/
cp -a /mnt/sdb1/operaprefs.ini.myremix64 /root/.opera/operaprefs.ini
cp -rf /mnt/sdb1/putty/. /root/.putty/.
mkdir /root/.mozilla/firefox/c3pp43bg.default/extensions/pinyin@sogou.com/
cp -rf /mnt/sdb1/pinyin@sogou.com/. /root/.mozilla/firefox/c3pp43bg.default/extensions/pinyin@sogou.com/.
cp -rf /mnt/sdb1/bookmarks-2011-04-19.json /root/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/
opera https://gmail.com http://www.malaysiakini.com/ http://www.merdekareview.com/ &
dolphin /mnt/sdb1/useful_mods_xzm &
dolphin /mnt/sda6/linux/useful_mods_xzm/test &
kwrite /mnt/sdb1/a.txt &
konsole &
umount /dev/sdb1
cp -a /mnt/sdb1/alsa-base.conf /etc/modprobe.d/
alsactl init Intel
sh /root/Desktop/add_module
exit
add_module script:-

Code: Select all

#!/bin/bash
activate /mnt/sdb1/useful_mods_xzm/mutt-1.5.21-x86_64-1.xzm
cp /mnt/sdb1/Muttrc /etc/mutt/Muttrc
activate /mnt/sda6/linux/useful_mods_xzm/test/nail-12.4-8-mdv2011.0.x86_64.xzm
activate /mnt/sdb1/useful_mods_xzm/sendmail-8.14.4-x86_64-2.xzm
activate /mnt/sdb1/useful_mods_xzm/procmail-3.22-x86_64-2.xzm
chmod 777 /etc/rc.d/rc.sendmail      
/etc/rc.d/rc.sendmail start
exit

User avatar
ponce
Contributor
Contributor
Posts: 89
Joined: 28 Dec 2010, 10:15
Location: IT
Contact:

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#35 by ponce » 13 May 2011, 05:37

ponce wrote:
fanthom wrote:"In pcman file manager if i choose open current folder as root, i get this message: Failed to execute child process "gksu" (No such file or directory)"
will check it as well...
to fix that we need gksu-polkit (with his dependencies, vala and libgee): I prepared a slackbuild and I'm testing it now, seems to work fine for using it instead of the original gksu, that is not the best solution in a policykit environment.
I'll post the three packages soon :)
here they are

http://ponce.cc/testing/lxde-addons/gksu-polkit/

after install you need also to change /etc/xdg/pcmanfm/LXDE/pcmanfm.conf and ~/.config/pcmanfm/LXDE/pcmanfm.conf (if present) to have

Code: Select all

su_cmd=gksu-polkit %s
instead of

Code: Select all

su_cmd=gksu '%s'
(also reachable through gui in pcmanfm advanced preferences)

obviously, this can be used also to launch other commands as root through policykit ;)

User avatar
fanthom
Site Admin
Site Admin
Posts: 4547
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#36 by fanthom » 13 May 2011, 08:50

@Pedro
1) porteus save.dat manager is fixed now. i have added "check_free_loop_device" function so it wont create unnecessary loops, added support for hidden (.*) files, added "sleep 2" before "losetup -d"
2) sound bug: when i start Porteus i have "Master" and "Front" for controlling the sound. when i open ff with website which contains flash multimedia (like youtube) then additional sound control channel is created in /dev/snd by udev. this channel is named "PCM" and is not visible for KDE (until you restart it) so when you start playing media by phonon (for example through dolphin) then PCM gets muted.
solution:
a) use "changes=" cheatcode to save alsamixer settings when PCM is present and visible for KDE
b) unmute PCM manually (or simply avoid phonon+falshplayer combination)

@all - Any ideas how to force udev to create PCM by default during boot time?

3) porteus_encrypter is also fixed

@Ahau
i would rewrite bloaders.txt due to Windows/linux users and not filesystems:
1) Windows users: syslinux will be used to install on FAT, they also and can use grub4dos for NTFS (examples on porteus.org)
2) Linux users:
a) extlinux will be used to install in ext(2,3,4)
b) syslinux will be used o install on FAT
c) extra: lilo can be used to install on every fs type (including NTFS). since BETA lilo offers "text menu" with same set of choices as syslinux - pls try it to find out more.

restore-mbr.txt
"MbrFix /drive 0 restorembr mbr.bak"
should be changed to
"MbrFix /drive 0 restorembr ../mbr.bak"
also
"(where sdx is the partition you are restoring to)"
to
"(where sdx is a drive you are restoring to)"
MBR must be restored to a drive (like sda) and not partition (like sda1)

@cttan
i need to track a particular module which is causing the hang to fix activate script. is there any place where i could download your modules mentioned above?
also: does the hang happen in KDE or LXDE?

@ponce
thanks a lot for new packages :)
vala seems to be little heavy. is there any way to use "xterm" as a helper which starts pcmanfm after su?
i was trying:
xterm -e su -c "pcmanfm"
but without luck :(

Cheers
Please add [Solved] to your thread title if the solution was found.

User avatar
ponce
Contributor
Contributor
Posts: 89
Joined: 28 Dec 2010, 10:15
Location: IT
Contact:

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#37 by ponce » 13 May 2011, 10:55

I don't think that will work, because the su-ed user won't be able by default to connect to the X display: that's one of the purposes of policykit.

I've no way to exclude vala besides getting away gksu-polkit also, but we got rid of gconf, gnome-vfs and friends... ;)
Last edited by ponce on 13 May 2011, 16:34, edited 1 time in total.

User avatar
Blaze
Moderator
Moderator
Posts: 1335
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus 3.2 Cinnamon x86_64
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#38 by Blaze » 13 May 2011, 11:11

fanthom,

1. Again i don't see a icons of txt files
Image - click for full details

2. In guest account i can't to make a modules (only in root account it work for me)
Image
Please to make a root account by default.

Thanks.
Linux porteus 4.12.7-porteus #1 SMP PREEMPT Sun Aug 13 17:38:30 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#39 by Ahau » 13 May 2011, 14:59

Updated drafts:

Code: Select all

***********************
* Porteus Bootloaders *
***********************

The bootloader that you install should be determined by your existing 
operating system and the file system of the partition on which you 
are installing Porteus.

WINDOWS
--------
If you are a Windows user, the SYSLINUX bootloader will be installed
on FAT or FAT32 formatted devices.  Grub4dos or lilo
can be used for NTFS formatted devices.

You can see your file system by right clicking on the drive you want 
to install Porteus on and selecting 'Properties'.

LINUX
--------
If you are a Linux user, then EXTLINUX should be installed on
ext(2,3 or 4) formatted devices, and SYSLINUX should be used
for FAT formatted devices.  

You can see your file system by opening a console and issuing:
df -T /dev/xxxN (where xxxN is your partition - e.g. hda1, sdb2, etc.)


NOTE:  Lilo can be used to boot every filesystem type, including NTFS.
Versions 1.0 and higher of Porteus include a text menu for Lilo with the
same options as the graphical SYSLINUX and EXTLINUX loaders. 

ALSO NOTE: a save.dat file will be automatically
created to save your changes if you are using a device
with a Windows (FAT or NTFS) filesystem.  You can access
your changes files by using the mloop command, e.g., 
'mloop /mnt/sdb1/porteus/save.dat'.  This will mount
your changes files to /mnt/loop.   

Code: Select all

Restoring your Master Boot Record

If you have accidentally overwritten your Master Boot Record (MBR) by running 
lin_start_here.sh or win_start_here.hta on a partition holding another 
operating system then you may be able to recover it.

WINDOWS
This applies only if you tried to run win_start_here.hta against a C: drive 
containing a windows install. It also assumes the most common instance where 
windows is on the first hard drive.

Inside the /boot/tools/ folder in the Porteus .iso there is a utility called 
MbrFix.exe. This utility is used to make a backup of the first 512 bytes of 
the first disk found, whenever win_start_here.hta is run. This backup, named 
mbr.bak, is placed on the root of the drive on which the win_start_here.hta 
script is run.

You can restore this backup to your drive's MBR by starting a command prompt 
as administrator, changing into the directory with MbrFix.exe (/boot/tools/) 
and running:
MbrFix /drive 0 restorembr ../mbr.bak

This utility has many other uses including rewriting a windows XP/Vista/7 MBR. 
You can see these other options by typing only MbrFix.exe

LINUX
If you chose to backup the MBR while running lin_start_here.sh then the first 
512 bytes of the chosen partition was backed up on the root of the drive 
from which you ran the lin_start_here.sh script. You can restore the MBR by 
copying the MBR backup elsewhere and issuing the following from a console:
dd if=/path/to/mbr.bak of=/dev/sdx bs=512 count=1 
(where sdx is the drive you are restoring).
Please take a look at our online documentation, here. Suggestions are welcome!

Pedro
White ninja
White ninja
Posts: 16
Joined: 11 Jan 2011, 01:57
Location: Portugal

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#40 by Pedro » 13 May 2011, 23:06

Is generate a system log option in porteus network setup tool working? No matter what i just can't get any log file in my desktop

Thanks
Pedro

User avatar
Blaze
Moderator
Moderator
Posts: 1335
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus 3.2 Cinnamon x86_64
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#41 by Blaze » 14 May 2011, 13:13

2. About
In guest account i can't to make a modules (only in root account it work for me)
if i type for guest account the password

Code: Select all

guest
I don't see a module, but if i type for guest account the password

Code: Select all

toor
I see a module.

3. In LXDE a icon of trash is full
Image

4. I have problem with my Russian localization for Porteus RC2 x86_64 :evil:
In /porteus/base/5-config-ru_RU_CP1251-0_0_2-noarch-2.xzm i have the folder /root/.kde4/share/config/ with file kxkbrc
but in Porteus RC2 a guest account is default and if i try to use another account my directory of /root/.kde4/share/config/ is broken.
Only root work for me. How fix it for all accounts (guest, root and a for a new accounts of users)?

Thanks.
Linux porteus 4.12.7-porteus #1 SMP PREEMPT Sun Aug 13 17:38:30 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

User avatar
fanthom
Site Admin
Site Admin
Posts: 4547
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#42 by fanthom » 14 May 2011, 16:56

@ponce
"su-ed user won't be able by default to connect to the X display"
it is possible as "xhost +local:root >/dev/null 2>&1" is run when kde/lxde starts.
(and guest is able to see "activation messages" after double click on a module)
anyway i can't get xterm to work with pcmanfm so will check gksu. thanks for the packages :)

@Blaze
"Again i don't see a icons of txt files"
i have explained that previously: to see icons on text files you need to disable "preview" in Dolphin -> View.
unfortunately you will loose the preview on graphic (jpeg/png) files.
which option is better?

"if i type for guest account the password I don't see a module"
added a title to xterm window: "Please enter root's password below"
also to xzm2dir, txz2xzm, etc....

"In LXDE a icon of trash is full"
that icon is not included in LXDE by default and comes from KDE desktop. unfortunately LXDE reads empty/full icons differently than KDE and seems to ignore "OnlyShowIn=KDE" setting. i'm out of clues how to fix this.... any help?

"I have problem with my Russian localization for Porteus.... How fix it for all accounts (guest, root and a for a new accounts of users)?"
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)

@Ahau
thanks for updated docs :)

@Perdo
reports are generated in /root/Desktop (info is misleading).
i have fixed it so now reports are generated on caller's desktop - thanks.

Cheers
Please add [Solved] to your thread title if the solution was found.

User avatar
Blaze
Moderator
Moderator
Posts: 1335
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus 3.2 Cinnamon x86_64
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#43 by Blaze » 14 May 2011, 18:48

"Again i don't see a icons of txt files"
i have explained that previously: to see icons on text files you need to disable "preview" in Dolphin -> View.
unfortunately you will loose the preview on graphic (jpeg/png) files.
which option is better?
yeah, but in AgiliaLinux distro all options look good for me :wall:
you must have kxkbrc file for each user in the system.
Great :wall: I have idea Image
Tomorrow i will try to realise it =) ...

Cheers
Linux porteus 4.12.7-porteus #1 SMP PREEMPT Sun Aug 13 17:38:30 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#44 by Rava » 15 May 2011, 07:24

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
Cheers!
Yours Rava

User avatar
Blaze
Moderator
Moderator
Posts: 1335
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus 3.2 Cinnamon x86_64
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Re: Porteus-v1.0-rc2-x86_64 "We are there" (almost)

Post#45 by Blaze » 15 May 2011, 11:59

you must have kxkbrc file for each user in the system.
... So I tried to realize my idea. I had no success...

I tried to tweaked /etc/rc.d/rc.keymap of my Russian localization

Code: Select all

#!/bin/sh

# Load the keyboard map and layout. More maps are in /usr/share/kbd/keymaps.
if [ -x /usr/bin/loadkeys ] ; then
/usr/bin/loadkeys ru-winkeys-cp1251_alt_sh.kmap # ru-cp1251.map
echo "[Layout]
EnableXkbOptions=true
LayoutList=ru,us
Use=true" > /$USER/.kde4/share/config/kxkbrc
fi
I tested in KDE and it work fine, but if i boot up Porteus i see it:
Image

Anybody can help me?
Linux porteus 4.12.7-porteus #1 SMP PREEMPT Sun Aug 13 17:38:30 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

Post Reply