Jump to content

dave843

Members
  • Posts

    11
  • Joined

  • Last visited

dave843's Achievements

New Here

New Here (1/7)

0

Reputation

  1. That initially didn't help either. I think the root of my problem is that my boot partition is a fat partition. And fat doesn't support symolic links. So there was no /boot/kernel.h file. Once I copied /boot/kernel.h-2.6.11-6mdksmp to /boot/kernel.h, it worked just fine. Thanks for the help
  2. I'm trying to install Vmware Server beta on my 2005LE, and I'm having trouble with the kernel source. Uname -r reports . But then the vmware server install reports I've looked around, and I can't seem to find a kernel-source-2.6-2.6.11-6mdksmp anywhere. It's not on my DVD (from a magazine), and not on any mirrors that I can find. Any idea where I can find that rpm?
  3. I don't think you can do this without installing Lilo/Grub. But you can do it without installing them in the MBR (which could be the problem GoBack had). The basic idea is to install Lilo on the first partition of your Linux install (NOT the MBR). Then make a boot floppy, and copy a file to the windows partition. You can then add an entry to the Windows boot loader which will call Lilo, and boot Linux like normal. I haven't tried this, but it here are some links: LinuxSolved (looks kind of old) NT OS Loader FedoraForum -- not the first post. Read about halfway down Hope this helps.
  4. Yes, grub is installed in /boot. But that is part of the root partition. Is it possible to create a new partition and move grub there? without re-installing?
  5. When you send mail, you use SMTP. When you receive mail, you use POP or IMAP.
  6. The question really is: "How can I choose which OS to boot from without selecting it at the bootloader prompt? (and without write access to the drive with grubl.lst on it)
  7. I have Mandrake 10.1 and Solaris 10 installed on 2 different hard drives, and they work just fine. I'm using Grub, and it can boot to either without any issues. I would like to be able to remotely choose which operating system to boot to. I initially thought I could just edit the /boot/grub/menu.lst file, and set the appropriate default. This works fine under linux, but Solaris can't write to the ext3 file system So I can remotely boot from Linux to Solaris, but then I can't get back to Linux... Is there a way to set a "boot this OS next time"? Or some other way to do this? [moved from Installing Mandrake by spinynorman]
  8. One more thing... When I was installing Mandrake, it wouldn't complete the tests for my video card (S3 Virge VGA). Every time I told it to test the settings, it would go to a solid blue screen, with an X as a mouse pointer. It wouldn't go anywhere else. I had to alt+ctrl+backspace out of it. I set it to not start X on boot. I logged in (text mode), ran XFdrake, and it tested and ran fine...
  9. Here is what happens when I try to start kicker (with the default kickerrc file in place): bash-2.05b$ kdeinit kicker kdeinit: Shutting down running client. --------------------------------- It looks like dcopserver is already running. If you are sure that it is not already running, remove /home/someuser/.DCOPserver_somemachine__0 and start dcopserver again. --------------------------------- QPixmap: Cannot create a QPixmap when no GUI is being used QPixmap: Cannot create a QPixmap when no GUI is being used KDE Daemon (kded) already running. QPixmap: Cannot create a QPixmap when no GUI is being used QPixmap: Cannot create a QPixmap when no GUI is being used kbuildsycoca running... Reusing existing ksycoca bash-2.05b$ ERROR: Communication problem with kicker, it probably crashed.
  10. Hi, I'm new to linux, but I've used Solaris (and other unix systems) for several years. I recently tried installing Mandrake 10.1 on an old pc I have that's not doing anything else. It seemed pretty straightforward, download the cds, and follow the instructions. Everything went pretty well until I logged into KDE. When I logged into KDE as a normal user, Kicker didn't work at all. I would get a couple of icons on the desktop (home, trash, ...), but no "start" button. I could right-click, and do a couple of things, but not having Kicker makes things a pain. I discovered that if I logged into KDE as root, I got Kicker, but I did not get the icons on the desktop, and right-clicking on the desktop didn't do anything. This problem only exists in KDE. If I log into icewm (sp?), everything works fine. Next, I figured I would make sure I'm running the latest versions of everything. So, I went into the Mandrake Control Center, and did the software update thing. I updated all packages, but that didn't help. I tried removing the ~/.kde/share/kickerrc file, but that didn't help either. I tried running "kdeinit kicker" and that didn't work, it said it couldn't communicate with kicker, it must have crashed. At this point I was wondering how the heck it worked for root, but not for a normal user. I tried to compare root's kickerrc file to the user one, but there is no .kde directory in /root. So, "find / -name kickerrc" gave me /usr/share/mdk/kde/root-interface/kickerrc. And that one is different than the user one. So, I copied that one over top of the user one, and voila, it works!! What is up with that? It also looks like it's only me, I can't find anything like this in search or google.
×
×
  • Create New...