Virtual packages cannot be installed by their name, instead they become installed in your system when you have installed a package providing the virtual package. Virtual packages allow other packages to not name a specific package as a dependency, in case there are several candidates. # pacman -S plasma-Ī virtual package is a special package which does not exist by itself, but is provided by one or more other packages. To install a number of packages sharing similar patterns in their names, one can use curly brace expansion. To install the version from the extra repository in this example, the repository needs to be defined in front of the package name: Sometimes there are multiple versions of a package in different repositories (e.g. To install a list of packages with regex (see this forum thread): To install a single package or list of packages, including dependencies, issue the following command: See System maintenance#Partial upgrades are unsupported and BBS#89328. In practice, do not run pacman -Sy package_name instead of pacman -Sy u package_name, as this could lead to dependency issues. The same configuration options when building it.Warning: When installing packages in Arch, avoid refreshing the package list without upgrading the system (for example, when a package is no longer found in the official repositories). So, the answer to your question is "both 'yes' and 'no.'" Yes, severalĭistros might use "Linux version X.Y.Z.," but No, they might not use Options that they have carefully selected, and include those (inīinary form) in their distributions. Lifting" for you: they'll compile one or more kernels, using config Generally speaking, a distro writer will do all of that "heavy (The same processĪlso determines which "kernel modules" are built.) Not included in "the Linux kernel" for your system. Subsequently determines exactly which blocks of source-code are or are Basically, a configurationįile is set up with a laundry-list of options, and this file "The Linux kernel" is a fairly complicated piece of software which canīe compiled in a number of different ways. Usually patches applied by many distros and they're compiled forĭifferent architectures and with different options.ĭistrowatch lists the default kernel used by each of the distros it Version nor the actual kernel even if the versions match, there are Nothing for you if you just "want it to work".Īlternatively, google for "eeepc kernel Ubuntu", maybe there are packages already compiled for Ubuntu.ĭifferent distros most certainly do NOT use the same kernel, not the This is actually easier than it sounds, but nonetheless requires some skill and reading. Probably the best solution would then be to use the git archive (mentioned at the kernel-eee Archlinux page) to copy the package sources to your computer, and then compile and install the kernel manually. I would not try to install that particular kernel package without understanding pacman. What that means is that while you can most likely use the tailored kernel with your Ubuntu system, you will run into problems when trying to install this kernel as a package, because Archlinux uses a different packaging system. However, the particular repository and package you mention are tailored to be used with the Archlinux distro. And since you can have multiple kernel alternatives that can be selected at boot time, you don't risk much: if your new kernel is not really working well with Ubuntu, you can always boot the system using the previous kernel. You can always install an alternative kernel without breaking anything in your system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |