How to run second KDE being chrooted?

**Aleu** · 08-08-2003, 09:21 PM

Hi guys,

I was wondering whether someone could guide me on how to run second KDE being chrooted.
I have followed the description:

--- cut ---
(b) Start X in the chrooted environment
You can run a second X server. So you don't have to exit from your
current session. This might not work for you, for example if you need the
nvidia driver to get X working. In that case you might skip (b) and try (c).
- go to terminal tty2 or any other which is free. you probably only
use tty1 at the moment.
You can switch between the screens with Alt+F1, Alt+F2.
Alt+F1 = tty1
Alt+F2 = tty2
Alt+F7 = xserver :0
Alt+F8 = xserver :1 (the one we are going to start

- setting the X server configuration up
Copy the /etc/X11/XF86Config-4 file from your computer to the knoppix
source to /etc/X11/. Don't forget to delete this file after you have
made the changes to the knoppix source.
- log in as the knoppix user (see steps from a).
- start X
export WINDOWMANAGER=/usr/X11R6/twm
export WINDOWMANAGER=/path/to/your/windowmanager (here I wrote /usr/bin/kde3?????)
startx -- :1
--- cut ---

but without success.
The second X server started but gave me an error that there is not enough RAM memory in my computer to run KDE. (I have 512 MB!)

I am kindly asking someone to guide me through.

Thanks

**MattT** · 08-08-2003, 10:21 PM

Use Ctrl+Alt+F1 and login as root. Start a second X with startx -- :1. Zero is you current X. Then use Ctrl+Alt+F7 and Ctrl+Alt+F8 as needed to switch between users.

**Aleu** · 08-08-2003, 11:13 PM

I don't want any second KDE session, but the one that will run from chrooted environment.

**Aleu** · 08-09-2003, 04:59 PM

People, please!!!

**NikiBob** · 08-10-2003, 06:04 AM

To start second KDE session in chrooted environment do the following:

1. In your "normal" X environment start xterm and type:

Code:

Xnest -ac :1

2.Go back to your chrooted source and type:

Code:

export DISPLAY=localhost:1
startkde

That is it!
Now you can work in boot X environment, chrooted and your "normal" working environment.

**MattT** · 08-10-2003, 06:08 AM

Have you tried method c of this Howto. This works fine for me every time. It is also the easiest way to work in my opinion. Don't know why you are getting memory error. I am also using 512MB. Hope you get it to work.

(c) Display X application in your "normal" X environment
Sometimes, I just need to make some minor changes to the knoppix source.
When I then need to test an X application it is often convenient to have
it opened in your "normal" X environment. Otherwise I would have
to exit from the knoppix source, close X and access the knoppix source
from again just to initiate X as shown in (b). Well, way to
much of work really. So here another way of doing it.
- start a second X server in your "normal" X environment
start xterm or any other x terminal and type:
Xnest -ac :1
- go back to your knoppix source start kde3
export DISPLAY=localhost:1
startkde
You can now work in both environments and do some tasks in one window
and some in the other.
(optionally)
- if it has to be another window manager than kde. try this
instead of typing startkde:
export WINDOWMANAGER=/usr/bin/gnome-session
export WINDOWMANAGER=/usr/X11R6/bin/twm
startx

**MattT** · 08-10-2003, 06:13 AM

NikiBob said it first. Do just what that says

**Aleu** · 08-10-2003, 11:34 PM

I love you guys!!! I knew I could count on you.

I love Linux a lot, but I love people who help solving problems even more.

Thanks

**jake5m** · 08-13-2003, 07:02 PM

Hi,
I am following the instructions above, and KDE does indeed begin to load in the Xnest window, but it hangs at the "initialising peripherals" stage in the splash screen. The console gives me the following:

Code:

bash-2.05b# startkde
/usr/bin/startkde: line 118: /dev/null: Permission denied
/usr/bin/startkde: line 122: /dev/null: Permission denied
ICE default IO error handler doing an exit(), pid = 1908, errno = 13
ICE default IO error handler doing an exit(), pid = 1910, errno = 2
kdeinit: Communication error with launcher. Exiting!
startkde: Starting up...
Session management error: Could not open network socket
Session management error: Could not open network socket
kbuildsycoca running...
Session management error: Could not open network socket

Any ideas as to what I'm doing wrong? (I am using V3.2-2003-07-26 )

Regards,
Jake

**jake5m** · 08-29-2003, 07:12 AM

I found out what my problem was! I was mounting the hard disk partition using the handy hard disk icon on the knoppix desktop (which mounts disks with "nodev") rather than a proper:

mount -o rw /dev/hda1 /mnt/hda1