| Re: /dev destroyed upon gnome install [message #10867 is a reply to message #10861] |
Tue, 06 March 2007 08:39   |
Vasily Tarasov
Messages: 1345
Registered: January 2006
|
Senior Member |
|
|
Hello,
| Quote: |
Now I can ssh to the VPS. 
But not ssh -X 
|
Hmm... What exact problem do you have? I can do ssh -X:
[HN]# ssh -X 172.0.0.2
Password:
Last login: Tue Mar 6 08:10:40 2007 from 192.168.X.Y
[VE]# exit
logout
Connection to 172.0.0.2 closed.
| Quote: |
BTW I think the solution about udev messing up /dev on Debian could be a FAQ or be placed in Wiki.
|
It'll be greatly appreciated!
| Quote: |
Is it correct to have different output of:
ls -l /vz/private/ID/dev
vzctl exec ID ls -l /dev
|
Yes it is absolutely ok. In few words the process of VE start is the following. First, /vz/private/ID/ is mirror-likely mounted on /vz/root/ID/ (using simfs filesystem). After that chroot to /vz/root/ID/ occurs and VE's init process is started. VE's udev init-script mounts tmpfs on /dev (/dev in VE, but /vz/root/dev on HN) and populates this newly mounted filesystem. So, when VE is started the output of
ls -l /vz/root/ID/dev
vzctl exec ID ls -l /dev
| Quote: |
Last as I told before while ssh is mandatory I don't really need to have gnome on the vps.
|
However, let's check, does it work, because for somebody else it can be mandatory to run gnome in VE.
| Quote: |
But the episode raised my fear about upgrade policies for vps. This time I had problem installing gnome but there could be some more dependencies problem hiding somewhere?
|
I undestand your fear. The only thing I can assure you is that the problems with udev are the only ones related to dependencies, I've encountered here at forum. So, from my expirience I can say that no problem should arise. However, there is no 100% guarantee as usual! 
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
