Because , you are a great contributor , and with your error , now , we know , the LLS by fanthom is not compatible with UnionFS Patch.i am mistaken.
For what I can say, the open and democratic way things are handled with Porteus so far gives us for a quite new distro a good head start in that direction, and I think we all agree that we want to keep it that way...Hamza wrote:Please , Do not say this :We are a community , and maybe , one day , we will in Top 10 of the Best Distro.i am mistaken.
Code: Select all
mkdir /tmp/{1,2,3,4}
mount pax-utils-0.2.3-x86_64-1ftm.img /tmp/1
mount portage-utils-0.4-x86_64-1ftm.img /tmp/2
mount sandbox-2.5-x86_64-1ftm.img /tmp/3
mount -n -o remount,add:1:/tmp/1=rr aufs /
mount -n -o remount,add:1:/tmp/2=rr aufs /
mount -n -o remount,add:1:/tmp/3=rr aufs /
mount -t aufs -o remount,verbose,del:/tmp/1 aufs /
mount -t aufs -o remount,verbose,del:/tmp/2 aufs /
mount -t aufs -o remount,verbose,del:/tmp/3 aufs /
*tries to see the light at the end of the tunnel* When I am not root... how can I activate or deactivate anyway?beny wrote:but deactivate isn't in right click menu only activate,how can i deactivate module from gui in porteus64,and why console tell me that module are activated if not...
It does work with rootshell -> starting konqueror AND using a rootshell and activate/deactivate, but like I said: that's not really GUI.beny wrote:i think with console,but i am not shure,
Code: Select all
./start_here.sh
[...]
Flushing filesystem buffers, this may take a while...
Setting up MBR on /dev/sdc...
./scripts/bootextlinux.sh: line 106: ./boot/syslinux/lilo: cannot execute binary file
Code: Select all
bash-3.1# file /mnt/sdc1/boot/syslinux/lilo
syslinux/lilo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), stripped
bash-3.1# file /mnt/sdb1/boot/syslinux/lilo
/mnt/sdb1/boot/syslinux/lilo: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, stripped
Double click on it. If it is already activated, the activate script will switch to deactivate.how can i deactivate module from gui in porteus64
From console i think activate script asks for root password.When I am not root... how can I activate or deactivate anyway?
Fanthom while testing in 32bit i found i can activate/deactivate and installpkg as much as i like without problem until i run into a large module that contains an ld.so.* file, whereupon it hangs. I was using 'for a in *.xzm; do activate $a; done` and same for installpkg. For me the large module was Virtualbox. I can't help thinking that this problem comes back to ldconfig and ld.so files. Can someone else test the theory?currently i'm fighting with aufs and 2.6.38 kernel. got few tips from Junjiro and making some tests.
I mean GUI as in: LXDE without any KDE stuff.brokenman wrote:Double click on it. If it is already activated, the activate script will switch to deactivate.
Perhaps a right click menu item should be added to deactivate, just to make things easier.
From console i think activate script asks for root password.[/quote]When I am not root... how can I activate or deactivate anyway?
Sadly, yes. I needed to fire up a 64 Bit Porteus on another machine to initialize the USB pendrive...I'm afraid if you are booted into a 32bit environment, you won't be able to work with 64bit binary.
If such lilo and syslinux is only needed for initialising the USB stick and not put on it like that it would be okay, since when running the stick the non-staically linked smaller version would again run since then it's a 64 bit system...fanthom wrote:the only solution is to compile static lilo and syslinux. unfortunately lilo itself is 700KB big while compiled statically.... didn't check syslinux/extlinux yet.
32bits are also affected as you wont be able to run 32bit lilo in pure 64bit environment (no multilib).
