Jump to content

Night_

Member
  • Posts

    37
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Night_'s Achievements

  1. @vorticalbox Yes, but installing a Deb manually isn't always the right way to do it, as the package might not be the same as the one available in the repository. If you wish to click on a GUI, using a package manager frontend like Synaptic. However if you ask me, overtime it's becomes a lot simpler to just open a terminal window and type in the command with the package name appended (e.g "apt-get install <package-name>").
  2. Once Grub (the bootloader) is installed once (usually done when installing any distro first) it can multiboot between whatever other distros you may wish to install in paralel. The tricky thing about having multiple distros though, is that each might have a different version for Grub in its repositories, which may cause situations during upgrades where each distro reinstalls and reconfigures Grub according to the package and configuration available to it. The simplest way to avoid this would be to let the distro with the most up-to-date Grub package in its repository to install the bootloader and have all upgrades to it be done as part of its update cycle, where the rest of the distros won't have the Grub package installed at all. In such a case the other distros would depend on the Grub update script from the "main" distro to have their boot entries added and updated, which is usually done automatically. So in a nutshell, what you will end up with is a single bootloader that is managed by a single distro and allows multibooting between all the other ones installed. The order of installation shouldn't matter as long as you make sure Grub gets auto-configured properly (which iirc should be done automatically and seamlessly anyway).
  3. A Q6600 isn't that underpowered. You can try using something like SME Server or ClearOS Community (Linux distros) if you need something that's relativly not too complicated to manage out of the box.
  4. @manikyath DHCP is only a piece of software. If it doesn't work out of the box, it can be reconfigured manually or swapped for another. There's no need to always strictly relay on what some company does with it.
  5. @manikyath And waste what otherwise could be a well-manifactured piece of hardware? Please, that's part of the reason why there's alternative open-source Linux or BSD based firmwares out there.
  6. @manikyath Some can issue address outside the range even if configured not to. Regardless though, system-wise it's still a better idea to let the DCHP handle this kind of thing if it already exists on the same network.
  7. Like @manikyath said, there shoud be an option in your router's DHCP server to lease an IP address based on your server's MAC address. Look around in your router administration panel, there should be a menu option for it somewhere. Otherwise you could always configure your server with a static IP that has the same subnet as the one used by your router. However doing so with a DHCP server on the network might eventually cause an address collision, so such a configuration might not always be a good option.
  8. @SCHISCHKA No, it might be fine in that regard. It's just that there might be hardware in it that doesn't work right off the bat with a fresh install.
  9. @jimpa1812 Try this first and see if the "Additional Drivers" menu appears, if it doesn't try installing the driver manually using the other command.
  10. @jimpa1812 Double check that you have network access, then run this: sudo apt-get update Afterwards try running the commands i mentioned previously.
  11. @jimpa1812 Apperantly the GUI is not pre-installed anymore, try running this first and then locating it again via the menu: sudo apt install software-properties-gtk software-properties-common
  12. Go to "Applications" > "System Settings" > "Additional Drivers", this built-in utility should autodetect and guide you on how to install the drivers you need via a GUI. A faster method would be to launch the installation proccess manually through a terminal windows by going to Applications > Terminal Emulator, then issuing the following command: sudo apt-get install fglrx-installer At any event, it's better to avoid installing the driver from the official website (e.g "the windows way"). Instead it's perfered to use the distro's repository, this way it minimizes the risk of having problems appear down the line.
  13. What are the full hardware specifications of the server?
  14. @Gameborn Huh, somehow i forgot that ever existed. Did it work fine for you?
×