larry wrote:
I do suspect that it is AMD64 support problems. If you follow the dependencies, they get all the way down to libs and so on, so I am thinking that they simply don't exist yet.The positive side to this is that if this is your VMware machine, you don't need X to have virtual machines. You can just connect remotely to the host using /usr/bin/vmware (default location). When you have it open, choose Remote Host. Give it the IP and credentials for a persone who can connect to vmware remotely (root by default). Once you are connected, you can create virtual hosts and work at the console of each vm. It's pretty slick.
I suppose if I left it alone and just did a dist-upgrade every few weeks, it might come to life....
M. Knisely wrote:Well, why are there dependency issues that apt can't handle for you? Is this an issue with Etch's repositories? Is the issue amd64 support problems?
Mike K.
larry wrote:
I installed Etch in the remaining free space on my lower array, got all the way through, and wrote grub to the MBR. When it rebooted, it still had the original Ubuntu grub configuration, and didn't know anything about no Debian.
I let Ubuntu come up, then mounted the Debian partition with the mount command. Then I checked to see that the /boot in my Debian partition (sdb1) looked right, it did. (I didn't look too closely) Obviously, Debian neglected to put the thing in the right partition. So I just copied it down to overwrite the Ubuntu one.
This basically lost both installations. It turns out that Debian got mixed up on the disk order, and set everything one number too high.
I booted from the Ubuntu DVD, mounted sda1 again, and edited menu.list. Changed every sdb1 to sda1, and every hd1 to hd0. That fixed it.
Then booted up Debian (2.6.16-2-amd64-generic) and tried to start gnome - all I got was the plain window manager. After poking around, I am seeing that gnome is only partially installed... the actual gnome-desktop-environment package will not install due to a nightmare of dependency conflicts.
I would scrap it now, except that 2 days ago I had the exact same distribution running fine in a vm on the same machine. Ideas?
To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field.
Mike K.
To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field.
